Technical impact
The vulnerability allows a registration request to be accepted without ensuring it was generated with the same token that originally registered the target cluster. This flaw lets an attacker associate a registration request with a cluster that was already registered with a different token, effectively hijacking that cluster’s identity. As a result, the attacker can gain access to the target cluster’s Fleet namespace and all associated resources, compromising confidentiality and integrity of cluster management data.
Affected Systems
The issue affects SUSE Rancher Fleet deployments in all releases prior to 0.16.4, specifically versions 0.12, 0.13.0-0.13.17, 0.14.0-0.14.12, 0.15.0-0.15.17, and 0.16.0-0.16.3.
Risk and Exploitability
The CVSS score of 7.9 indicates a moderate to high severity. The EPSS score is not available, but there is no evidence of exploitation in the field to date and it is not listed in the CISA KEV catalog. The likely attack path is through the Fleet cluster registration interface, which can be accessed remotely by any entity that can reach the Fleet API. Attackers do not need privileged credentials at this stage; they only need to craft a registration request with a valid token from a different cluster.