Cluster identity takeover in Fleet cluster registration allows access to another cluster's Fleet namespace
Affects Fleet in SUSE Rancher releases up to 0.16.2, including all of 0.12 and earlier; fixed in 0.16.3, 0.14.12 and 0.13.17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.16.3, 0.15.17, 0.14.12, 0.13.17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SUSE Rancher Fleet, the GitOps tool used to manage deployments across Kubernetes clusters, is affected by this vulnerability. An attacker could take over the identity of an existing managed cluster during registration, gaining access to another cluster's Fleet namespace.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A security vulnerability was discovered in SUSE Rancher Fleet's cluster registration flow, in Fleet versions before 0.12, 0.13.0 up to 0.13.17, 0.14.0 up to 0.14.12, 0.15.0 up t o 0.15.17 and 0.16.0 up to 0.16.3. The cluster identity claimed by a registration request was accepted without being bound to the registration token that the request was made with. As a result, a registration request could be associated with a managed cluster that was originally registered with a different registration token.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Fleett
From 0.16.0 · fixed in 0.16.3; From 0.15.0. · fixed in 0.15.17; From 0.14.0 · fixed in 0.14.12; From 0.13 · fixed in 0.13.17; through 0.12
References 1
GitHub · rancher/fleet
Questions about CVE-2026-104615
What does this mean?
A cluster registered with Fleet can be taken over by an attacker who holds a valid registration token for the workspace and knows the cluster's client identifier. The attacker then gets credentials for that cluster's Fleet namespace, which exposes the Secrets and ConfigMaps synced there and allows limited changes to bundle deployment and cluster status.Source: github.com
Am I affected, and how do I check?
Fleet 0.16.0 before 0.16.3, 0.15.0 before 0.15.17, 0.14.0 before 0.14.12, 0.13 before 0.13.17, and 0.12 and earlier. Check the installed Fleet version against these ranges. Cross-tenant impact also requires a shared Fleet workspace holding clusters from different tenants, which is the default single-workspace model.Source: github.com
What should I do about it?
Upgrade to the fixed release on the same branch: 0.16.3, 0.14.12 or 0.13.17. The 0.15 branch fix is listed as 0.15.17 in the range data but as 0.15.8 in the vendor's fix note, so confirm the target version before upgrading.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data