EUVD-2026-88335Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable authenticated tenant (PR:L) with low complexity; I assess S:C because the flaw lets one tenant act with cluster-admin across another tenant's authorization scope on the shared cluster.
Primary rating from Vendor (suse).
CVSS VectorVendor: suse
Lifecycle Timeline
6DescriptionCVE.org
A vulnerability has been identified within Rancher Manager where the Fleet agent wrote resources to downstream clusters using its own cluster-admin credentials instead of the ServiceAccount pinned to the deployment. It affects multi-tenancy environments where different tenants share the same downstream clusters, for example different privileged or untrusted teams inside the same organization. This could lead to overwritten configuration files.
This issue affected SUSE Rancher Fleet 0.16 before 0.16.2, 0.15 before 0.15.7, and 0.14 before 0.14.11.
Articles & Coverage 1
AnalysisAI
Privilege escalation in SUSE Rancher Fleet (0.14.x before 0.14.11, 0.15.x before 0.15.7, and 0.16.x before 0.16.2) lets a low-privileged tenant - an authenticated user able to push a Fleet Bundle or GitRepo - have resources written to a shared downstream cluster under the Fleet agent's own cluster-admin credentials rather than the ServiceAccount pinned to the deployment, allowing that tenant to overwrite configuration owned by other tenants. Exploitation is gated by topology: it only matters in multi-tenant Fleet deployments where privileged and untrusted teams share the same downstream cluster, since single-tenant or per-tenant-isolated clusters have no crossed trust boundary. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
No credit card · 7-day full trial
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires a multi-tenant Fleet deployment in which different tenants (e.g., privileged/trusted and untrusted teams) SHARE the same downstream cluster, and the attacker must already hold a low-privileged tenant identity able to create/push a Fleet Bundle or GitRepo (PR:L, AV:N, no user interaction). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine privilege-boundary vulnerability rather than a high-CVSS-but-low-risk paper cut, but its real-world impact is gated by a specific deployment condition. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade Fleet to 0.16.2 (0.16.x), 0.15.7 (0.15.x), or 0.14.11 (0.14.x); these fixed versions remove the condition in which the agent writes downstream resources with its own cluster-admin credentials instead of the deployment-pinned ServiceAccount, so patching is the primary and complete remediation - see advisory GHSA-q9v4-358v-r8q5 (https://github.com/rancher/fleet/security/advisories/GHSA-q9v4-358v-r8q5). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all SUSE Rancher Fleet deployments to determine if you are running affected versions (0.14.x before 0.14.11, 0.15.x before 0.15.7, or 0.16.x before 0.16.2) and identify multi-tenant environments where privileged and untrusted teams share the same downstream cluster; immediately restrict the ability to create Fleet Bundles or GitRepos to only trusted administrators and enable audit logging for all Fleet resource changes. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Same weakness CWE-250 – Execution with Unnecessary Privileges
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: ImportantShare
External POC / Exploit Code
Leaving vuln.today