Technical impact
The vulnerability permits an ordinary user, by creating a Fleet Cluster object in a namespace they control, to associate that object with a kubeconfig secret containing administrative credentials for the management cluster. The Fleet controller then installs and manages a Fleet agent on the management cluster using those credentials, effectively allowing the user to run their Fleet content with cluster‑admin privileges. This flaw is rooted in Improper Privilege Management (CWE‑250) and can compromise the entire cluster’s security state, providing a user who normally has only limited permissions full control over the management cluster. The impact is therefore a complete privilege escalation to cluster‑admin level, granting full read, write, and administrative permissions across all cluster resources.
Affected Systems
SUSE Rancher Fleet affects versions 0.16.0 through 0.16.3, 0.15.0 through 0.15.8, 0.14.0 through 0.14.12, 0.13.0 through 0.13.17, and possibly earlier releases. All of these releases run the Fleet controller that can reference kubeconfig secrets without adequate restriction, making them vulnerable if a user can create or modify Fleet Cluster objects in their namespaces.
Risk and Exploitability
The CVSS score of 9.1 marks this vulnerability as critical. No EPSS score is available, so the current exploitation probability is uncertain; however, the absence of a KEV listing does not reduce the severity. The likely attack path involves an attacker creating or modifying a Fleet Cluster object that points to a privileged kubeconfig secret. Because the controller does not enforce namespace‑level or role‑based restrictions on the referenced secrets, the attacker can cause the controller to perform privileged operations on the management cluster, thereby achieving cluster‑admin privileges. This escalation of privileges can lead to full control of cluster resources, data exfiltration, and further lateral movement within the environment.