Threats affecting pkg:github/github.com/rancher/rancher

CVE-2024-22031 is a high-severity authorization vulnerability in SUSE Rancher. It allows a user who can create a project in one cluster to create a project with the same name in another cluster, thereby gaining unauthorized access to the other project. This occurs because the namespace for storing project-related resources is based on the project name, leading to privilege escalation across clusters.

An unauthenticated update of public UI settings could be used by remote attackers to execute a stored cross-site scripting attack in the Rancher UI, in SUSE Rancher 2.15 before 2.15.2, 2.14 before 2.14.6, 2.13 before 2.13.10, 2.12 before 2.12.14 and 2.11 before 2.11.18.

CVE-2026-88805 is a high-severity vulnerability in SUSE Rancher versions 2.15.0 and 2.15.1 where insufficient session expiration occurs due to incorrect credential cleaning on logout. This flaw allows remote attackers to retain access credentials even after the user logs out, potentially leading to unauthorized access. The issue is fixed starting from version 2.15.2.

A flaw was found in Rancher Manager. When a non-administrative caller supplied a label selector naming a different user, the ext.cattle.io/v1 Token store dropped its internal owner filter instead of returning an empty result. Any authenticated user could therefore list and watch every other user's tokens, disclosing token metadata and the stored salted hash of the bearer token. This issue affects Rancher: before 2.15.1.

A flaw was found in Rancher Manager. The SAML assertion replay protection introduced by the fix for CVE-2026-44946 recorded consumed assertion IDs in a per-process cache, so each replica only detected replays that reached the same pod. In a high-availability deployment, an attacker holding a captured assertion could replay it once against every other replica to obtain additional authenticated sessions as the victim. This issue affects Rancher: before 2.15.1.

A flaw was found in Rancher Manager. Project Secrets were propagated into a namespace based only on its `field.cattle.io/projectId` annotation, without verifying that the referenced project belonged to the same downstream cluster. A user able to create namespaces on one cluster could set the annotation to a project ID from another cluster and have that project's secrets copied into a namespace under their control. This issue affects Rancher: before 2.15.1.

A flaw was found in Rancher Manager. The GlobalRole controller derived the target ClusterRole name from the user-settable `authz.management.cattle.io/cr-name` annotation and overwrote that object's rules without verifying ownership. A user with delegated GlobalRole create or update permission could point the annotation at any existing ClusterRole, such as `cluster-admin`, and revoke the permissions of every principal bound to it. The change persists after the malicious GlobalRole is deleted. This issue affects Rancher: before 2.15.1.

A flaw was found in Rancher Manager. The /v3/users update path did not enforce immutability of a User resource's `username` and `principalIds` fields. A user holding the `update` verb on `users.management.cattle.io` could inject a foreign identity provider principal into any account, so that the next login by the owner of that principal was bound to the victim's account and inherited its role bindings. This issue affects Rancher: before 2.15.1.

CVE-2026-44945 is a critical privilege escalation vulnerability in SUSE Rancher's impersonation middleware. An authenticated user with the default global user role can escalate privileges to gain full administrative access to the Rancher control plane and all downstream clusters it manages. The vulnerability affects Rancher versions from 2.11.0 before 2.11.16, 2.12.0 before 2.12.12, 2.13.0 before 2.13.8, and 2.14.0 before 2.14.2.

A missing clean-up in the legacy Project Role Template Binding (PRTB) reconciler in Rancher versions 2.13.0 up to 2.13.7 and 2.14.0 up to 2.14.3 allowed users to retain unauthorized Pod Security Admission (PSA) permissions after an administrator removes those permissions from a RoleTemplate.

A SAML authentication replay vulnerability in Rancher's Assertion Consumer Service (ACS) handler did not enforce one-time use of SAML assertion, potentially allowing person in the middle attacks against Rancher, affecting Rancher 2.14.0 before 2.14.3,

Incorrect authentication caching in the team member ship expansion of the Rancher Github authentication provider caused it granting principal access to any logged in user, in 2.13 before 2.13.6 and 2.14 before 2.14.2.

Improper privilege handling could be used by users with Project Owner role to escalate privileges, in Rancher versions 2.14 before 2.14.2, 2.13 before 2.13.6, and 2.12 before 2.12.10.

A command injection vulnerability in the Rancher Manager cluster before 2.14.2 import endpoint /v3/import/{token}_{clusterId}.yaml through unsanitized YAML parameters could allow remote attackers to break out of an image, and execute e.g. malicious containers.

CVE-2026-25705 is a high-severity path traversal vulnerability in SUSE Rancher's Extensions component. It allows a malicious UI extension to inject code by exploiting the compressedEndpoint field in a UIPlugin deployment. Successful exploitation can lead to overwriting Rancher binaries or configurations, tampering with cluster state, writing to the host filesystem if hostPath volumes are mounted, and chaining with other attack vectors. The vulnerability affects Rancher versions 2.10.11, 2.12.0, 2.13.0, and 2.

A vulnerability has been identified within Rancher Manager, where using self-signed CA certificates and passing the -skip-verify flag to the Rancher CLI login command without also passing the –cacert flag results in the CLI attempting to fetch CA certificates stored in Rancher’s setting cacerts.