EUVD-2026-88294Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Network-reachable registration with low complexity and low privilege (PR:L, must register into shared namespace); attacker gains other tenants' Bundles/secrets (C:H) with minor targeting integrity impact (I:L), no availability effect.
Primary rating from Vendor (suse).
CVSS VectorVendor: suse
Lifecycle Timeline
6DescriptionCVE.org
A cross-tenant authorization issue was discovered in SUSE Rancher Fleet. During agent-initiated cluster registration, cluster labels supplied by the registering agent, including labels in the reserved management.cattle.io/ namespace such as the cluster display name label, were applied to the resulting upstream Cluster object. Because Fleet resolves GitRepo and Bundle targets from those cluster labels, a party able to register a cluster into a Fleet workspace namespace shared with other tenants could cause its own cluster to satisfy targeting rules that administrators intended for a different cluster. This affects SUSE Rancher Fleet 0.16 before 0.16.1, 0.15 before 0.15.6, 0.14 before 0.14.10, 0.13 before 0.13.15, 0.12 before 0.12.19 and older versions.
Articles & Coverage 1
AnalysisAI
Cross-tenant authorization bypass in SUSE Rancher Fleet allows a party who can perform agent-initiated cluster registration into a Fleet workspace namespace shared with other tenants to inject attacker-controlled cluster labels - including reserved management.cattle.io/ labels such as the cluster display name - that are then persisted onto the upstream Cluster object. Because Fleet resolves GitRepo and Bundle targeting from those labels, the attacker's own cluster can be made to satisfy targeting rules administrators intended for a different tenant's cluster, causing content such as Git repos and bundles to be deployed to the wrong cluster. …
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 the attacker can perform agent-initiated cluster registration into a Fleet workspace namespace that is SHARED with other tenants, and where administrators use cluster-label-based GitRepo/Bundle targeting rules. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a real but conditional multi-tenancy authorization flaw, not a mass-exploitation threat. … 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 patches are available: upgrade Fleet to 0.16.1, 0.15.6, 0.14.10, 0.13.15, or 0.12.19 depending on your release line, following the upgrade instructions in the advisory at https://github.com/rancher/fleet/security/advisories/GHSA-h9p5-fp5h-qpqr, and update the corresponding Rancher version that bundles Fleet. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Rancher Fleet installations and confirm current versions against the affected ranges (Fleet 0.16 before 0.16.1, 0.15 before 0.15.6, 0.14 before 0.14.10, 0.13 before 0.13.15, 0.12 before 0.12.19, and older releases), identify any multi-tenant deployments that share a Fleet workspace namespace between tenants, and audit upstream Cluster objects for unexpected or attacker-supplied reserved management.cattle.io/ labels, especially cluster display name. …
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-290 – Authentication Bypass by Spoofing
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: ImportantShare
External POC / Exploit Code
Leaving vuln.today