SUSE has addressed a critical privilege escalation vulnerability within Rancher that could enable a low-privileged authenticated user to gain administrative control over the management plane and all downstream Kubernetes clusters managed by Rancher This article explores downstream kubeconfigs authentication. . The issue is tracked as CVE-2026-44945 and documented in the GitHub advisory GHSA-v584-7w32-jwpq, with a CVSS score of 9.1 and classified as an unintended proxy/confused-deputy weakness.
When a request arrived, Rancher extracted a cluster identifier from the URL and performed a Kubernetes SubjectAccessReview (SAR) against the specified downstream cluster. Users assigned the default global role on Rancher can typically import clusters, allowing an attacker to register a disposable environment like k3d, kind, or minikube as the authorization oracle for the escalation attempt.
An attacker gaining local-cluster administrative access could read secrets containing downstream kubeconfigs, authentication-provider credentials, LDAP bind passwords, OIDC client secrets, and SAML signing keys. They could also create or modify GlobalRoleBindings, establish persistent administrative access, and use Rancher’s central management capabilities to compromise all enrolled downstream clusters. The patch changes the authorization boundary by evaluating SAR-based impersonation checks with a fixed client for the local Rancher management cluster, rather than selecting one from the request URL.
Teams without immediate patch access should restrict cluster-import permissions, review GlobalRoleBinding changes, audit privileged API activity, rotate potentially exposed credentials, and monitor any suspicious Rancher management-plane access.
