CVE-2026-93538: CWE-290 Authentication bypass by spoofing in SUSE Rancher
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.
AI Analysis
Technical Summary
This vulnerability arises from SUSE Rancher Fleet's handling of cluster labels during agent-initiated cluster registration. Labels, including those in the reserved management.cattle.io/ namespace such as the cluster display name, are applied to the upstream Cluster object. Since Fleet uses these labels to resolve GitRepo and Bundle targets, an attacker registering a cluster in a shared Fleet workspace namespace can manipulate cluster labels to impersonate or satisfy targeting rules meant for other tenants' clusters, leading to cross-tenant authorization bypass.
Potential Impact
An attacker able to register a cluster in a shared Fleet workspace namespace can bypass intended authorization controls by spoofing cluster labels. This allows the attacker’s cluster to be targeted by GitRepo and Bundle configurations meant for other tenants, potentially leading to unauthorized access or manipulation of resources associated with those clusters. The confidentiality impact is high, integrity impact is low, and availability is not affected.
Mitigation Recommendations
A fix is available in SUSE Rancher Fleet versions 0.16.1, 0.15.6, 0.14.10, 0.13.15, and 0.12.19. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-93538: CWE-290 Authentication bypass by spoofing in SUSE Rancher
Description
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.
CVSS v3.1
Score 7.1high
Affected software
SUSE
Rancher
pkg:github/FleetRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from SUSE Rancher Fleet's handling of cluster labels during agent-initiated cluster registration. Labels, including those in the reserved management.cattle.io/ namespace such as the cluster display name, are applied to the upstream Cluster object. Since Fleet uses these labels to resolve GitRepo and Bundle targets, an attacker registering a cluster in a shared Fleet workspace namespace can manipulate cluster labels to impersonate or satisfy targeting rules meant for other tenants' clusters, leading to cross-tenant authorization bypass.
Potential Impact
An attacker able to register a cluster in a shared Fleet workspace namespace can bypass intended authorization controls by spoofing cluster labels. This allows the attacker’s cluster to be targeted by GitRepo and Bundle configurations meant for other tenants, potentially leading to unauthorized access or manipulation of resources associated with those clusters. The confidentiality impact is high, integrity impact is low, and availability is not affected.
Mitigation Recommendations
A fix is available in SUSE Rancher Fleet versions 0.16.1, 0.15.6, 0.14.10, 0.13.15, and 0.12.19. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- suse
- Date Reserved
- 2026-09-18T09:08:10.294Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aba7aabf7a7c54106cb9e87
Added to database: 09/28/2026, 14:33:15 UTC
Last enriched: 09/28/2026, 14:47:44 UTC
Last updated: 09/29/2026, 01:57:22 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.