Rancher
Monthly
Stored cross-site scripting in the SUSE Rancher UI allows unauthenticated remote attackers to inject malicious script through updates to public UI settings, which then executes in the browser of any user-including administrators-who later views the affected interface. Affected versions are 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. Vendor CVSS 3.1 rates this 9.6, while our independent assessment lowers the availability impact to low; no public exploit identified at time of analysis, and exploitation requires network reachability to the Rancher management endpoint plus a victim loading the UI.
Remote attackers holding a previously issued Rancher session token can retain access even after the legitimate user logs out in SUSE Rancher 2.15 before 2.15.2, because the server fails to clear credentials on logout (CWE-613). This session persistence flaw carries a CVSS 3.1 base score of 8.1 (High) with network reach, low complexity, no attacker privileges (PR:N), and required user interaction (UI:R) for the logout. No public exploit identified at time of analysis; exploitation is limited to scenarios where the attacker already possesses a valid token, such as shared-device or stolen-session situations.
Privilege escalation in SUSE Rancher Fleet (0.14.x before 0.14.11, 0.15.x before 0.15.7, and 0.16.x before 0.16.2) lets a low-privileged tenant - an authenticated user able to push a Fleet Bundle or GitRepo - have resources written to a shared downstream cluster under the Fleet agent's own cluster-admin credentials rather than the ServiceAccount pinned to the deployment, allowing that tenant to overwrite configuration owned by other tenants. Exploitation is gated by topology: it only matters in multi-tenant Fleet deployments where privileged and untrusted teams share the same downstream cluster, since single-tenant or per-tenant-isolated clusters have no crossed trust boundary. Rated 8.8 by the vendor (the independent assessment scores it higher, 9.9, because the trust boundary crossing changes scope); no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis.
Cross-tenant authorization bypass in SUSE Rancher Fleet allows a party who can perform agent-initiated cluster registration into a Fleet workspace namespace shared with other tenants to inject attacker-controlled cluster labels - including reserved management.cattle.io/ labels such as the cluster display name - that are then persisted onto the upstream Cluster object. Because Fleet resolves GitRepo and Bundle targeting from those labels, the attacker's own cluster can be made to satisfy targeting rules administrators intended for a different tenant's cluster, causing content such as Git repos and bundles to be deployed to the wrong cluster. The flaw affects Fleet 0.16 before 0.16.1, 0.15 before 0.15.6, 0.14 before 0.14.10, 0.13 before 0.13.15, 0.12 before 0.12.19 and older releases; exploitation is conditional on a multi-tenant deployment with a shared workspace namespace and label-based targeting, requires a low-privileged authenticated position (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, 7.1), and no public exploit code has been identified at time of analysis.
Cross-cluster secret exfiltration in Rancher Manager before 2.15.1 allows any authenticated user with namespace-creation rights on one downstream cluster to read Project Secrets belonging to a completely separate downstream cluster. The secretsController propagates secrets based solely on the user-writable `field.cattle.io/projectId` annotation, skipping validation that the referenced project belongs to the same cluster - a classic CWE-639 insecure direct object reference pattern. No public exploit or CISA KEV listing has been identified at time of analysis; the vendor-confirmed fix is v2.15.1.
Token store authorization bypass in Rancher Manager before 2.15.1 allows any authenticated user to enumerate every other user's session tokens by supplying a crafted label selector to the ext.cattle.io/v1 Token API. The owner-scoped filter that restricts results to the calling user's own tokens is silently dropped when the caller supplies a label selector naming a different user, instead of returning an empty result set as intended. Exposed data includes token metadata and salted bearer-token hashes, creating an offline cracking risk. No public exploit is identified at time of analysis; a vendor-released patch is available in v2.15.1.
SAML assertion replay bypass in Rancher Manager before v2.15.1 allows unauthenticated network attackers to obtain additional authenticated management sessions as a victim user in high-availability deployments. The per-process in-memory cache that tracks consumed SAML assertion IDs - introduced by the CVE-2026-44946 fix - is not shared across pod replicas, so a captured assertion can be replayed once against each replica that has not yet seen it, yielding one unauthorized session per targeted replica. All SAML identity providers supported by Rancher are affected, and a vendor-released patch is available in v2.15.1. No public exploit code or CISA KEV listing has been identified at time of analysis.
Privilege escalation in Rancher Manager before 2.15.1 allows any user with delegated GlobalRole create or update permission to permanently destroy cluster-wide Kubernetes RBAC policies by hijacking arbitrary ClusterRoles. The GlobalRole controller resolved its target ClusterRole by reading the user-settable `authz.management.cattle.io/cr-name` annotation rather than deriving the name from the GlobalRole's own identity, enabling an authenticated attacker to redirect the controller at any ClusterRole - including `cluster-admin` - and overwrite its rules. The corrupted permissions persist in the Kubernetes object store even after the malicious GlobalRole is deleted, making this a durable, stealthy integrity attack. No public exploit has been identified at time of analysis.
Cleartext registration token exposure in Rancher allows a low-privileged user to obtain perpetually valid cluster join tokens and enlist rogue nodes into downstream Kubernetes clusters. The tokens - used to authenticate nodes and agents during cluster bootstrapping - are stored without encryption or expiration and are reachable through at least four distinct channels: the Rancher API, etcd, stored automation artifacts, and direct filesystem access on enrolled nodes. The CVSS scope-change flag (S:C) accurately reflects that successful exploitation extends attacker influence beyond the Rancher management plane into downstream cluster workloads, secrets, and compute. No public exploit has been identified at time of analysis, and no CISA KEV listing exists.
Unbounded memory allocation in Rancher Manager's API audit logging middleware enables unauthenticated remote attackers to crash the Rancher management plane via memory exhaustion. When API audit logging is enabled, the audit copyReqBody middleware - positioned ahead of Rancher's APIBodyLimitingHandler in the handler chain - reads entire HTTP request bodies into memory on public login endpoints with no size cap, bypassing the default 1 MiB limit. An attacker sending a small number of concurrent oversized requests to these endpoints can exhaust server memory and terminate the Rancher Manager process, rendering the Rancher API and UI unavailable and severing management control of all downstream Kubernetes clusters. No public exploit has been identified at time of analysis.
Information disclosure in SUSE Rancher AI Agent 1.0 before 1.0.2 writes API keys and raw LLM response text (which may contain sensitive data) into logfiles when the DEBUG loglevel is enabled, letting a local attacker with access to those logs harvest credentials and confidential model output. Rated CVSS 4.0 base 7.0, the flaw requires local access and high privileges plus a non-default debug configuration. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Authentication bypass in SUSE Rancher's in-cluster admission webhook (rancher-webhook) lets a network-adjacent, unauthenticated attacker forge FleetWorkspace admission payloads so that workspace-related Kubernetes objects are created with attacker-chosen identity data. Affected releases span Rancher 0.7.0–0.7.10, 0.8.0–0.8.7, 0.9.0–0.9.6 and 0.10.0–0.10.7, with integrity impact but no direct confidentiality or availability loss. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the issue is documented in SUSE/Rancher advisory GHSA-h83p-cq95-vph4.
SAML assertion replay in Rancher's Assertion Consumer Service (ACS) handler lets a person-in-the-middle who captures a victim's SAML response reuse that assertion to authenticate as the victim, because the handler never enforces one-time use. Rancher 2.14.0 through 2.14.2 are affected, and because Rancher governs downstream Kubernetes clusters, a successful replay can yield administrative control. No public exploit identified at time of analysis; the issue is not on the CISA KEV list, and the carried CVSS 4.0 base score is 9.5 driven largely by the scope/subsequent-system impact.
Privilege escalation in Rancher 2.13 (before 2.13.6) and 2.14 (before 2.14.2) lets any authenticated user gain principal access they should not hold, because the GitHub authentication provider incorrectly caches the result of team membership expansion. The flaw (CWE-303, CVSS 8.8) means a low-privileged GitHub-authenticated user can be granted access tied to other principals/teams, effectively bypassing intended authorization. No public exploit identified at time of analysis and it is not listed in CISA KEV.
Privilege escalation in SUSE Rancher (Kubernetes management platform) allows a user holding the Project Owner role to improperly escalate their privileges beyond their assigned project scope, per advisory GHSA-vx8h-4prv-g744. Affected releases are 2.14 before 2.14.2, 2.13 before 2.13.6, and 2.12 before 2.12.10. There is no public exploit identified at time of analysis, but the CVSS 4.0 base score of 9.4 and scope-changing impact mean a successful escalation can compromise cluster-wide confidentiality, integrity, and availability.
Command injection in Rancher Manager’s cluster import endpoint enables remote attackers to deploy malicious containers on downstream Kubernetes clusters using a crafted URL. The vulnerability affects Rancher versions 2.10.0–2.10.12, 2.11.0–2.11.14, 2.12.0–2.12.10, 2.13.0–2.13.6, and 2.14.0–2.14.2, and has a CVSS 4.0 score of 9.4. No active exploitation has been confirmed, and the EPSS exploitation probability is low at 1.11%, though a vendor-supplied patch is available.
SUSE Rancher Fleet versions 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, and 0.13 before 0.13.16 allow an attacker with low-privilege bundle deployment rights to modify labels and annotations on Kubernetes namespaces that the bundle's pinned identity is not authorized to change. The flaw arises from inconsistent authorization checks when a bundle requests namespace metadata updates via the namespaceLabels and namespaceAnnotations options. No public exploit code has been identified at time of analysis, and the CVSS 3.1 score of 6.5 reflects integrity-only impact (C:N/I:H/A:N) requiring existing low privileges on the network.
Rancher Fleet 0.16.0 and 0.16.1 accept requests to the gitjob webhook receiver without verification whenever no webhook secret is configured, allowing any party with network reach to that endpoint to alter the spec.pollingInterval field of matching GitRepo resources in any namespace - including namespaces where the caller holds no Kubernetes credentials or RBAC. The assessed vector is unauthenticated remote (AV:N/PR:N), and impact is deliberately narrow: only a single configuration field can be changed, with no arbitrary spec edits, secret exposure, or workload execution and no confidentiality loss. Only Fleet 0.16.0/0.16.1 are affected, Fleet 0.16.2 and all pre-0.16 releases are not, and no public exploit code has been identified at time of analysis.
Relative path traversal (CWE-23) in SUSE Rancher Fleet allows an authenticated attacker with either Git push access to a repository referenced by a GitRepo resource or Kubernetes RBAC permission to create or modify a GitRepo (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) to read files from the filesystem of the bundle-processing environment and have their contents emitted into the generated Bundle resource. The most valuable target is Helm registry credential material that Fleet makes available to the bundle-processing job when per-path Helm credentials are configured, letting the attacker exfiltrate secrets they have no Kubernetes RBAC permission to read. All Fleet branches below 0.16.2, 0.15.7, 0.14.11, 0.13.16 and 0.12.20 are affected; there is no public exploit identified at time of analysis and no evidence of confirmed active exploitation, so this is a moderate privilege-boundary-crossing disclosure rather than an emergency.
SUSE Observability deployments using the rancher-extension-stackstate extension are susceptible to credential exposure where service tokens are stored insecurely, enabling an attacker with local access and low privileges to obtain them and potentially escalate privileges. This moderate-severity issue (CWE-312) requires pre-existing minimal access to the affected system and has a confidentiality-only impact, with no public exploit identified at time of analysis. The assessed CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) underscores that exploitation is limited to environments where tokens are improperly stored.
Identity injection in Rancher Manager before 2.15.1 allows a privileged Rancher user to hijack any other user's account by overwriting immutable identity provider fields. The /v3/users update API failed to strip principalIds and username from update payloads, so a user holding the update verb on users.management.cattle.io could inject an external IdP principal they control into any target account. The next time the attacker authenticates via that injected IdP principal, Rancher binds the session to the victim's account and the attacker inherits all its role bindings. No public exploit is identified at time of analysis, and a vendor patch is available in version 2.15.1.
Cluster ID enumeration in SUSE Rancher exposes a reliable oracle via the unauthenticated `/v3/import/{token}_{clusterId}.yaml` endpoint, which performs cluster object retrieval before token validation. Remote unauthenticated attackers can distinguish valid cluster IDs (HTTP 502, triggered by a nil pointer dereference in `pkg/systemtemplate/private_registry.go` when private registry secrets exist) from non-existent ones (HTTP 200), leaking the presence and private-registry configuration status of clusters. This is not listed in CISA KEV and no public exploit code has been identified, but the zero-prerequisite network accessibility makes enumeration trivially scriptable.
Denial of service in Rancher's dynamiclistener TLS library allows network-accessible attackers to exhaust certificate Subject Alternative Name capacity on both the Rancher server and cattle-cluster-agent components. By sending a large volume of TLS requests each presenting a distinct Server Name Indication (SNI) hostname, an attacker causes the dynamiclistener library to continuously append new SANs to the serving certificate until its size exceeds TLS handshake limits, breaking all TLS communication on the affected listener. No public exploit has been identified at time of analysis, and CISA KEV status is not confirmed; however, exploitation is straightforward given the low technical barrier.
Path traversal in Rancher Fleet's ImageScan subsystem (CWE-23) allows authenticated remote attackers to escape intended directory boundaries and trigger denial of service across four active release branches (0.12.x through 0.15.x). The flaw appears to have been introduced in the 0.12.0 series and persisted undetected through at least sixteen subsequent patch releases, indicating the ImageScan component lacked adequate path sanitization for an extended period. No public exploit code or active exploitation has been identified; the CVSS 4.0 vector (PR:L) confirms exploitation requires authenticated access, materially limiting opportunistic attack surface.
Privilege persistence in SUSE Rancher allows project users to retain Pod Security Admission (PSA) permissions even after an administrator revokes those permissions from a RoleTemplate, due to a missing cleanup step in the legacy Project Role Template Binding (PRTB) reconciler. Affected versions are Rancher 2.13.0 through 2.13.7 and 2.14.0 through 2.14.3. An attacker with a pre-existing role assignment can continue to bypass PSA policies enforced at the project level, defeating administrative intent and potentially deploying workloads that violate the cluster's security posture. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV.
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. [CVSS 8.3 HIGH]
A Improper Privilege Management vulnerability in SUSE Rancher causes permission changes in Azure AD not to be reflected to users while they are logged in the Rancher UI. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
An Improper Privilege Management vulnerability in SUSE Rancher allowed standard users to leverage their existing permissions to manipulate Kubernetes secrets in the local cluster, resulting in the. Rated high severity (CVSS 8.0), this vulnerability is low attack complexity. No vendor patch available.
Improper Privilege Management vulnerability in SUSE Rancher allows Privilege Escalation. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
An Improper Authorization vulnerability in SUSE Rancher, allows any user who has permissions to create/edit cluster role template bindings or project role template bindings (such as cluster-owner,. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A Cleartext Transmission of Sensitive Information vulnerability in SUSE Rancher, Rancher allows attackers on the network to read and change network data due to missing encryption of data transmitted. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.
A Reliance on Untrusted Inputs in a Security Decision vulnerability in Rancher allows users in the cluster to act as others users in the cluster by forging the "Impersonate-User" or. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A Improper Access Control vulnerability in Rancher, allows users in the cluster to make request to cloud providers by creating requests with the cloud-credential ID. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A Incorrect Permission Assignment for Critical Resource vulnerability in Rancher allows users in the cluster to modify resources they should not have access to. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Rancher allows remote attackers to execute JavaScript via malicious links. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Rancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
An issue was discovered that affects the following versions of Rancher: v2.0.0 through v2.0.13, v2.1.0 through v2.1.8, and v2.2.0 through 2.2.1. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
A vulnerability exists in Rancher before 2.2.4 in the login component, where the errorMsg parameter can be tampered to display arbitrary content, filtering tags but not special characters or symbols. Rated medium severity (CVSS 4.7), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
In Rancher 2 through 2.2.3, Project owners can inject additional fluentd configuration to read files or execute arbitrary commands inside the fluentd container. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Rancher 1 and 2 through 2.2.3, unprivileged users (if allowed to deploy nodes) can gain admin access to the Rancher management plane because node driver options intentionally allow posting certain. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Rancher 2.0.0 through 2.1.5, project members have continued access to create, update, read, and delete namespaces in a project after they have been removed from it. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Rancher Labs rancher server 1.2.0+ is vulnerable to authenticated users disabling access control via an API call. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity.
Stored cross-site scripting in the SUSE Rancher UI allows unauthenticated remote attackers to inject malicious script through updates to public UI settings, which then executes in the browser of any user-including administrators-who later views the affected interface. Affected versions are 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. Vendor CVSS 3.1 rates this 9.6, while our independent assessment lowers the availability impact to low; no public exploit identified at time of analysis, and exploitation requires network reachability to the Rancher management endpoint plus a victim loading the UI.
Remote attackers holding a previously issued Rancher session token can retain access even after the legitimate user logs out in SUSE Rancher 2.15 before 2.15.2, because the server fails to clear credentials on logout (CWE-613). This session persistence flaw carries a CVSS 3.1 base score of 8.1 (High) with network reach, low complexity, no attacker privileges (PR:N), and required user interaction (UI:R) for the logout. No public exploit identified at time of analysis; exploitation is limited to scenarios where the attacker already possesses a valid token, such as shared-device or stolen-session situations.
Privilege escalation in SUSE Rancher Fleet (0.14.x before 0.14.11, 0.15.x before 0.15.7, and 0.16.x before 0.16.2) lets a low-privileged tenant - an authenticated user able to push a Fleet Bundle or GitRepo - have resources written to a shared downstream cluster under the Fleet agent's own cluster-admin credentials rather than the ServiceAccount pinned to the deployment, allowing that tenant to overwrite configuration owned by other tenants. Exploitation is gated by topology: it only matters in multi-tenant Fleet deployments where privileged and untrusted teams share the same downstream cluster, since single-tenant or per-tenant-isolated clusters have no crossed trust boundary. Rated 8.8 by the vendor (the independent assessment scores it higher, 9.9, because the trust boundary crossing changes scope); no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis.
Cross-tenant authorization bypass in SUSE Rancher Fleet allows a party who can perform agent-initiated cluster registration into a Fleet workspace namespace shared with other tenants to inject attacker-controlled cluster labels - including reserved management.cattle.io/ labels such as the cluster display name - that are then persisted onto the upstream Cluster object. Because Fleet resolves GitRepo and Bundle targeting from those labels, the attacker's own cluster can be made to satisfy targeting rules administrators intended for a different tenant's cluster, causing content such as Git repos and bundles to be deployed to the wrong cluster. The flaw affects Fleet 0.16 before 0.16.1, 0.15 before 0.15.6, 0.14 before 0.14.10, 0.13 before 0.13.15, 0.12 before 0.12.19 and older releases; exploitation is conditional on a multi-tenant deployment with a shared workspace namespace and label-based targeting, requires a low-privileged authenticated position (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, 7.1), and no public exploit code has been identified at time of analysis.
Cross-cluster secret exfiltration in Rancher Manager before 2.15.1 allows any authenticated user with namespace-creation rights on one downstream cluster to read Project Secrets belonging to a completely separate downstream cluster. The secretsController propagates secrets based solely on the user-writable `field.cattle.io/projectId` annotation, skipping validation that the referenced project belongs to the same cluster - a classic CWE-639 insecure direct object reference pattern. No public exploit or CISA KEV listing has been identified at time of analysis; the vendor-confirmed fix is v2.15.1.
Token store authorization bypass in Rancher Manager before 2.15.1 allows any authenticated user to enumerate every other user's session tokens by supplying a crafted label selector to the ext.cattle.io/v1 Token API. The owner-scoped filter that restricts results to the calling user's own tokens is silently dropped when the caller supplies a label selector naming a different user, instead of returning an empty result set as intended. Exposed data includes token metadata and salted bearer-token hashes, creating an offline cracking risk. No public exploit is identified at time of analysis; a vendor-released patch is available in v2.15.1.
SAML assertion replay bypass in Rancher Manager before v2.15.1 allows unauthenticated network attackers to obtain additional authenticated management sessions as a victim user in high-availability deployments. The per-process in-memory cache that tracks consumed SAML assertion IDs - introduced by the CVE-2026-44946 fix - is not shared across pod replicas, so a captured assertion can be replayed once against each replica that has not yet seen it, yielding one unauthorized session per targeted replica. All SAML identity providers supported by Rancher are affected, and a vendor-released patch is available in v2.15.1. No public exploit code or CISA KEV listing has been identified at time of analysis.
Privilege escalation in Rancher Manager before 2.15.1 allows any user with delegated GlobalRole create or update permission to permanently destroy cluster-wide Kubernetes RBAC policies by hijacking arbitrary ClusterRoles. The GlobalRole controller resolved its target ClusterRole by reading the user-settable `authz.management.cattle.io/cr-name` annotation rather than deriving the name from the GlobalRole's own identity, enabling an authenticated attacker to redirect the controller at any ClusterRole - including `cluster-admin` - and overwrite its rules. The corrupted permissions persist in the Kubernetes object store even after the malicious GlobalRole is deleted, making this a durable, stealthy integrity attack. No public exploit has been identified at time of analysis.
Cleartext registration token exposure in Rancher allows a low-privileged user to obtain perpetually valid cluster join tokens and enlist rogue nodes into downstream Kubernetes clusters. The tokens - used to authenticate nodes and agents during cluster bootstrapping - are stored without encryption or expiration and are reachable through at least four distinct channels: the Rancher API, etcd, stored automation artifacts, and direct filesystem access on enrolled nodes. The CVSS scope-change flag (S:C) accurately reflects that successful exploitation extends attacker influence beyond the Rancher management plane into downstream cluster workloads, secrets, and compute. No public exploit has been identified at time of analysis, and no CISA KEV listing exists.
Unbounded memory allocation in Rancher Manager's API audit logging middleware enables unauthenticated remote attackers to crash the Rancher management plane via memory exhaustion. When API audit logging is enabled, the audit copyReqBody middleware - positioned ahead of Rancher's APIBodyLimitingHandler in the handler chain - reads entire HTTP request bodies into memory on public login endpoints with no size cap, bypassing the default 1 MiB limit. An attacker sending a small number of concurrent oversized requests to these endpoints can exhaust server memory and terminate the Rancher Manager process, rendering the Rancher API and UI unavailable and severing management control of all downstream Kubernetes clusters. No public exploit has been identified at time of analysis.
Information disclosure in SUSE Rancher AI Agent 1.0 before 1.0.2 writes API keys and raw LLM response text (which may contain sensitive data) into logfiles when the DEBUG loglevel is enabled, letting a local attacker with access to those logs harvest credentials and confidential model output. Rated CVSS 4.0 base 7.0, the flaw requires local access and high privileges plus a non-default debug configuration. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Authentication bypass in SUSE Rancher's in-cluster admission webhook (rancher-webhook) lets a network-adjacent, unauthenticated attacker forge FleetWorkspace admission payloads so that workspace-related Kubernetes objects are created with attacker-chosen identity data. Affected releases span Rancher 0.7.0–0.7.10, 0.8.0–0.8.7, 0.9.0–0.9.6 and 0.10.0–0.10.7, with integrity impact but no direct confidentiality or availability loss. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the issue is documented in SUSE/Rancher advisory GHSA-h83p-cq95-vph4.
SAML assertion replay in Rancher's Assertion Consumer Service (ACS) handler lets a person-in-the-middle who captures a victim's SAML response reuse that assertion to authenticate as the victim, because the handler never enforces one-time use. Rancher 2.14.0 through 2.14.2 are affected, and because Rancher governs downstream Kubernetes clusters, a successful replay can yield administrative control. No public exploit identified at time of analysis; the issue is not on the CISA KEV list, and the carried CVSS 4.0 base score is 9.5 driven largely by the scope/subsequent-system impact.
Privilege escalation in Rancher 2.13 (before 2.13.6) and 2.14 (before 2.14.2) lets any authenticated user gain principal access they should not hold, because the GitHub authentication provider incorrectly caches the result of team membership expansion. The flaw (CWE-303, CVSS 8.8) means a low-privileged GitHub-authenticated user can be granted access tied to other principals/teams, effectively bypassing intended authorization. No public exploit identified at time of analysis and it is not listed in CISA KEV.
Privilege escalation in SUSE Rancher (Kubernetes management platform) allows a user holding the Project Owner role to improperly escalate their privileges beyond their assigned project scope, per advisory GHSA-vx8h-4prv-g744. Affected releases are 2.14 before 2.14.2, 2.13 before 2.13.6, and 2.12 before 2.12.10. There is no public exploit identified at time of analysis, but the CVSS 4.0 base score of 9.4 and scope-changing impact mean a successful escalation can compromise cluster-wide confidentiality, integrity, and availability.
Command injection in Rancher Manager’s cluster import endpoint enables remote attackers to deploy malicious containers on downstream Kubernetes clusters using a crafted URL. The vulnerability affects Rancher versions 2.10.0–2.10.12, 2.11.0–2.11.14, 2.12.0–2.12.10, 2.13.0–2.13.6, and 2.14.0–2.14.2, and has a CVSS 4.0 score of 9.4. No active exploitation has been confirmed, and the EPSS exploitation probability is low at 1.11%, though a vendor-supplied patch is available.
SUSE Rancher Fleet versions 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, and 0.13 before 0.13.16 allow an attacker with low-privilege bundle deployment rights to modify labels and annotations on Kubernetes namespaces that the bundle's pinned identity is not authorized to change. The flaw arises from inconsistent authorization checks when a bundle requests namespace metadata updates via the namespaceLabels and namespaceAnnotations options. No public exploit code has been identified at time of analysis, and the CVSS 3.1 score of 6.5 reflects integrity-only impact (C:N/I:H/A:N) requiring existing low privileges on the network.
Rancher Fleet 0.16.0 and 0.16.1 accept requests to the gitjob webhook receiver without verification whenever no webhook secret is configured, allowing any party with network reach to that endpoint to alter the spec.pollingInterval field of matching GitRepo resources in any namespace - including namespaces where the caller holds no Kubernetes credentials or RBAC. The assessed vector is unauthenticated remote (AV:N/PR:N), and impact is deliberately narrow: only a single configuration field can be changed, with no arbitrary spec edits, secret exposure, or workload execution and no confidentiality loss. Only Fleet 0.16.0/0.16.1 are affected, Fleet 0.16.2 and all pre-0.16 releases are not, and no public exploit code has been identified at time of analysis.
Relative path traversal (CWE-23) in SUSE Rancher Fleet allows an authenticated attacker with either Git push access to a repository referenced by a GitRepo resource or Kubernetes RBAC permission to create or modify a GitRepo (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) to read files from the filesystem of the bundle-processing environment and have their contents emitted into the generated Bundle resource. The most valuable target is Helm registry credential material that Fleet makes available to the bundle-processing job when per-path Helm credentials are configured, letting the attacker exfiltrate secrets they have no Kubernetes RBAC permission to read. All Fleet branches below 0.16.2, 0.15.7, 0.14.11, 0.13.16 and 0.12.20 are affected; there is no public exploit identified at time of analysis and no evidence of confirmed active exploitation, so this is a moderate privilege-boundary-crossing disclosure rather than an emergency.
SUSE Observability deployments using the rancher-extension-stackstate extension are susceptible to credential exposure where service tokens are stored insecurely, enabling an attacker with local access and low privileges to obtain them and potentially escalate privileges. This moderate-severity issue (CWE-312) requires pre-existing minimal access to the affected system and has a confidentiality-only impact, with no public exploit identified at time of analysis. The assessed CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) underscores that exploitation is limited to environments where tokens are improperly stored.
Identity injection in Rancher Manager before 2.15.1 allows a privileged Rancher user to hijack any other user's account by overwriting immutable identity provider fields. The /v3/users update API failed to strip principalIds and username from update payloads, so a user holding the update verb on users.management.cattle.io could inject an external IdP principal they control into any target account. The next time the attacker authenticates via that injected IdP principal, Rancher binds the session to the victim's account and the attacker inherits all its role bindings. No public exploit is identified at time of analysis, and a vendor patch is available in version 2.15.1.
Cluster ID enumeration in SUSE Rancher exposes a reliable oracle via the unauthenticated `/v3/import/{token}_{clusterId}.yaml` endpoint, which performs cluster object retrieval before token validation. Remote unauthenticated attackers can distinguish valid cluster IDs (HTTP 502, triggered by a nil pointer dereference in `pkg/systemtemplate/private_registry.go` when private registry secrets exist) from non-existent ones (HTTP 200), leaking the presence and private-registry configuration status of clusters. This is not listed in CISA KEV and no public exploit code has been identified, but the zero-prerequisite network accessibility makes enumeration trivially scriptable.
Denial of service in Rancher's dynamiclistener TLS library allows network-accessible attackers to exhaust certificate Subject Alternative Name capacity on both the Rancher server and cattle-cluster-agent components. By sending a large volume of TLS requests each presenting a distinct Server Name Indication (SNI) hostname, an attacker causes the dynamiclistener library to continuously append new SANs to the serving certificate until its size exceeds TLS handshake limits, breaking all TLS communication on the affected listener. No public exploit has been identified at time of analysis, and CISA KEV status is not confirmed; however, exploitation is straightforward given the low technical barrier.
Path traversal in Rancher Fleet's ImageScan subsystem (CWE-23) allows authenticated remote attackers to escape intended directory boundaries and trigger denial of service across four active release branches (0.12.x through 0.15.x). The flaw appears to have been introduced in the 0.12.0 series and persisted undetected through at least sixteen subsequent patch releases, indicating the ImageScan component lacked adequate path sanitization for an extended period. No public exploit code or active exploitation has been identified; the CVSS 4.0 vector (PR:L) confirms exploitation requires authenticated access, materially limiting opportunistic attack surface.
Privilege persistence in SUSE Rancher allows project users to retain Pod Security Admission (PSA) permissions even after an administrator revokes those permissions from a RoleTemplate, due to a missing cleanup step in the legacy Project Role Template Binding (PRTB) reconciler. Affected versions are Rancher 2.13.0 through 2.13.7 and 2.14.0 through 2.14.3. An attacker with a pre-existing role assignment can continue to bypass PSA policies enforced at the project level, defeating administrative intent and potentially deploying workloads that violate the cluster's security posture. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV.
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. [CVSS 8.3 HIGH]
A Improper Privilege Management vulnerability in SUSE Rancher causes permission changes in Azure AD not to be reflected to users while they are logged in the Rancher UI. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
An Improper Privilege Management vulnerability in SUSE Rancher allowed standard users to leverage their existing permissions to manipulate Kubernetes secrets in the local cluster, resulting in the. Rated high severity (CVSS 8.0), this vulnerability is low attack complexity. No vendor patch available.
Improper Privilege Management vulnerability in SUSE Rancher allows Privilege Escalation. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
An Improper Authorization vulnerability in SUSE Rancher, allows any user who has permissions to create/edit cluster role template bindings or project role template bindings (such as cluster-owner,. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A Cleartext Transmission of Sensitive Information vulnerability in SUSE Rancher, Rancher allows attackers on the network to read and change network data due to missing encryption of data transmitted. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.
A Reliance on Untrusted Inputs in a Security Decision vulnerability in Rancher allows users in the cluster to act as others users in the cluster by forging the "Impersonate-User" or. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A Improper Access Control vulnerability in Rancher, allows users in the cluster to make request to cloud providers by creating requests with the cloud-credential ID. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A Incorrect Permission Assignment for Critical Resource vulnerability in Rancher allows users in the cluster to modify resources they should not have access to. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
A Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Rancher allows remote attackers to execute JavaScript via malicious links. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Rancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
An issue was discovered that affects the following versions of Rancher: v2.0.0 through v2.0.13, v2.1.0 through v2.1.8, and v2.2.0 through 2.2.1. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
A vulnerability exists in Rancher before 2.2.4 in the login component, where the errorMsg parameter can be tampered to display arbitrary content, filtering tags but not special characters or symbols. Rated medium severity (CVSS 4.7), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
In Rancher 2 through 2.2.3, Project owners can inject additional fluentd configuration to read files or execute arbitrary commands inside the fluentd container. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Rancher 1 and 2 through 2.2.3, unprivileged users (if allowed to deploy nodes) can gain admin access to the Rancher management plane because node driver options intentionally allow posting certain. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Rancher 2.0.0 through 2.1.5, project members have continued access to create, update, read, and delete namespaces in a project after they have been removed from it. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Rancher Labs rancher server 1.2.0+ is vulnerable to authenticated users disabling access control via an API call. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity.