Critical Rancher Flaw Lets Authenticated Users Gain Full Admin Access to All Managed Clusters

A critical privilege-escalation vulnerability in SUSE Rancher could allow a low-privilege, authenticated user to gain administrative control of the Rancher management plane and every downstream Kubernetes cluster it manages.

This issue is tracked as CVE-2026-44945 and GHSA-v584-7w32-jwpq, affecting Rancher releases 2.11.0 through 2.11.15, 2.12.0 through 2.12.11, 2.13.0 through 2.13.7, and 2.14.0 through 2.14.1.

Rancher has released fixes in versions 2.11.16, 2.12.12, 2.13.8, and 2.14.4. The advisory rates this flaw as Critical, with a CVSS v3.1 score of 9.1.

Critical Rancher Flaw

The defect is found in Rancher’s impersonation middleware, specifically in the request handling located at pkg/auth/requests/impersonate.go.

It is classified as a cross-cluster authorization flaw, categorized under CWE-441, which describes a confused-deputy weakness. Essentially, Rancher checks whether an impersonation request is authorized in one Kubernetes cluster, but executes it against another: the local Rancher management cluster.

Rancher extracts a cluster identifier from the request URL and uses it to run a Kubernetes SubjectAccessReview (SAR) against the referenced downstream cluster.

However, the management API then processes the request through the local management cluster using the scaledContext service account. Impersonation headers, such as Impersonate-User, Impersonate-Group, and Impersonate-Extra, re forwarded unchanged to the local Kubernetes API by the Norman proxy store.

This separation between authorization and execution creates an escalation path. An attacker who controls RBAC permissions on any registered downstream cluster can craft a request to impersonate a privileged identity, like system:masters, within that cluster.

Rancher subsequently forwards the impersonation context to its local cluster, where the privileged request is executed. As a result, the attacker gains administrative control of Rancher rather than merely elevated permissions in the downstream cluster used to pass the SAR check.

Exploitation requires a valid Rancher session and RBAC control over at least one downstream cluster. Notably, the advisory states that a user assigned Rancher’s default user global role can import a personally controlled cluster.

A disposable k3d, kind, or minikube deployment is sufficient, meaning the attacker does not need prior access to a production cluster, an elevated Rancher role, or user interaction.

Once exploited, this flaw can expose all Rancher secrets, including kubeconfig files, authentication provider credentials, LDAP bind passwords, OIDC client secrets, and SAML signing keys.

An attacker could also create or modify GlobalRoleBindings, establishing persistent control across all clusters managed by the affected Rancher instance.

The patches enforce SAR-based impersonation checks with a fixed client for the local management cluster. They also ensure that the middleware obtains the authenticated identity from the request context instead of relying on client-supplied impersonation headers.

Organizations must upgrade immediately. If patching is delayed, administrators should audit and restrict who can register downstream clusters.

However, Rancher cautions that this only reduces exposure and is not a complete mitigation. Security researcher BenTheCyberOne reported this vulnerability for exposed Rancher deployments worldwide.

Stop new phishing & malware before they compromise your business. Integrate live intel from 15K SOCs around the world