Threat Intelligence Database

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.

CVE-2026-55998 is a medium severity vulnerability in SUSE Rancher versions 2.11.0, 2.12.0, 2.13.0, and 2.14.0. The issue arises from an endpoint that retrieves cluster objects before validating tokens, causing different HTTP responses based on the existence of cluster IDs and their configuration. This discrepancy allows attackers to reliably enumerate valid cluster IDs.

CVE-2026-59675 is a high-severity vulnerability in SUSE Rancher versions 2.12.0, 2.13.0, and 2.14.0. When API audit logging is enabled, the middleware reads the entire HTTP request body into memory without size limits on login endpoints, bypassing the intended 1 MiB cap. This allows an unauthenticated attacker to send very large request bodies, causing excessive memory consumption and potential denial of service by crashing the Rancher Manager process, which disrupts API and UI availability and management of downstream clusters.

CVE-2026-55996 is a denial-of-service vulnerability in SUSE Rancher affecting multiple TLS listeners. The issue arises because the dynamiclistener library appends any hostname presented via Server Name Indication (SNI) to the serving certificate's Subject Alternative Names (SANs) without effective filtering. An unauthenticated attacker with network access can exploit this by sending many TLS requests with distinct hostnames, causing the certificate to grow excessively large and resulting in TLS handshake failures and service disruption.

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.