Security Advisories and CVEs

Rancher is committed to informing the community of security issues in our products. Rancher will publish security advisories and CVEs (Common Vulnerabilities and Exposures) for issues we have resolved. New security advisories are also published in Rancher’s GitHub security page.

ID Description Date Resolution

ID	Description	Date	Resolution
CVE-2026-75036	Fixed a vulnerability in Fleet’s Helm template preprocessing where untrusted bundle content could cause the Fleet controller to disclose cluster metadata and information about hosts reachable from the controller.	26 August 2026	Fleet v0.16.1, Fleet v0.15.6, Fleet v0.14.10, Fleet v0.13.15, Fleet v0.12.19
CVE-2026-55998	Fixed a security vulnerability in Rancher’s unauthenticated cluster import endpoint where an attacker could enumerate valid cluster IDs and detect private registry usage by observing distinguishable HTTP response codes.	30 July 2026	Rancher v2.14.4, Rancher v2.13.8, Rancher v2.12.12, and Rancher v2.11.16.
CVE-2026-55996	Fixed a security vulnerability where an unauthenticated attacker with cluster-internal network access could flood TLS listeners in `cattle-cluster-agent` and in the Rancher server with requests containing arbitrary hostnames, causing serving certificates to accumulate excessive Subject Alternative Names (SANs) until TLS handshakes failed. The fix applies CN filtering to reject attacker-supplied SNI hostnames and caps the maximum number of SANs per certificate.	30 July 2026	Rancher v2.14.4, Rancher v2.13.8, Rancher v2.12.12, and Rancher v2.11.16.
CVE-2026-44945	Fixed a critical security vulnerability in Rancher’s impersonation middleware (`pkg/auth/requests/impersonate.go`) where an authenticated user with the default `user` global role could exploit a cross-cluster impersonation flaw to impersonate privileged identities, including `system:masters`, against the local Rancher management cluster. This allowed full administrative takeover of the Rancher control plane and all managed downstream clusters and secrets.	30 July 2026	Rancher v2.14.4, Rancher v2.13.8, Rancher v2.12.12, and Rancher v2.11.16.
CVE-2026-44949	Fixed a security vulnerability in rancher-webhook where the FleetWorkspace mutating admission webhook performed side effects without authenticating requests, allowing a pod inside the cluster to create arbitrary namespaces and inject RBAC bindings.	29 June 2026	Rancher v2.14.3, Rancher v2.13.7, Rancher v2.12.11 and Rancher v2.11.15
CVE-2026-44946	Fixed a security vulnerability in Rancher’s SAML authentication handler where a valid signed SAML response could be replayed by an attacker who had also captured the victim’s pre-authentication SAML state cookie, allowing the attacker to create a separate authenticated session with the victim’s permissions. All SAML providers (Okta, Ping, ADFS, Keycloak, Shibboleth) were affected.	29 June 2026	Rancher v2.14.3, Rancher v2.13.7, Rancher v2.12.11 and Rancher v2.11.15
CVE-2026-44939	Rancher now validates the `authImage` parameter in cluster import manifests to prevent YAML injection attacks.	27 May 2026	Rancher v2.14.2, Rancher v2.13.6, v2.12.10, v2.11.14, and v2.10.12
CVE-2026-25705	Rancher now protects against arbitrary file access via path traversal in Rancher Extensions. Note by default only users with administrative permissions can deploy UI extensions unless explicit permission is granted to other users.	30 Apr 2026	Rancher v2.14.1, v2.13.5, v2.12.9, and v2.11.13
CVE-2025-62879	Rancher now provides new versions of the Rancher Backup chart which prevent the leak of secret S3 credentials via the Rancher Backup pod log.	29 Jan 2026	Rancher v2.13.2, v2.12.6, v2.11.10, and v2.10.11
CVE-2025-67601	Rancher now removes the ability to fetch CA certificates stored in Rancher’s setting `cacerts` when using the `login` command.	29 Jan 2026	Rancher v2.13.2, v2.12.6, v2.11.10, and v2.10.11
CVE-2023-32199	Rancher now removes the corresponding ClusterRoleBindings whenever the admin GlobalRole or its GlobalRoleBindings are deleted. Previously orphaned ClusterRoleBindings were marked with the annotation `authz.cluster.cattle.io/admin-globalrole-missing=true`.	23 Oct 2025	Rancher v2.12.3 and v2.11.7
CVE-2024-58260	Setting the username of one user as the same username of another user causes an error when either user attempts to log in. Therefore, a user with the `Manage Users` permission could potentially deny any user, including admins, from logging in. To prevent this, usernames have been made immutable once set, and it is not possible to update or create a user with a username that is already in use.	25 Sep 2025	Rancher v2.12.2, v2.11.6, v2.10.10, and v2.9.12
CVE-2024-58267	The Rancher CLI is modified to print the `requestId` more visibly than as part of the login URL. It also adds a `cli=true` origin marker to the URL. The dashboard is modified to recognize the presence of the `requestId` and uses that to show a warning message to the user, asking for verification that they initiated a CLI login with the related Id. The non-presence of the origin marker enables the dashboard to distinguish between the modified CLI and older CLI’s, and adjust the message accordingly.	25 Sep 2025	Rancher v2.12.2, v2.11.6, v2.10.10, and v2.9.12
CVE-2025-54468	`Impersonate-*` headers are removed for requests made through the `/meta/proxy` Rancher endpoint (e.g. when cloud credentials are being created) as the headers may contain identifiable and/or sensitive information.	25 Sep 2025	Rancher v2.12.2, v2.11.6, v2.10.10, and v2.9.12
CVE-2024-58259	POSTs to the Rancher API endpoints are now limited to 1 Mi; this is configurable through the settings if you need a larger limit. The Rancher authentication endpoints are configured independently of the main public API (as you might need bigger payloads in the other API endpoints). Suppose you need to increase the maximum allowed payload for authentication. In that case, you can set the environment variable `CATTLE_AUTH_API_BODY_LIMIT` to a quantity, e.g., 2 Mi, which would allow larger payloads for the authentication endpoints.	28 Aug 2025	Rancher v2.12.1, v2.11.5, v2.10.9 and v2.9.11
CVE-2024-52284	Following a recent change excluding Helm values files from bundles, an edge case subsisted where the values files referenced in `fleet.yaml` with your directory name (e.g., `my-dir/values.yaml` instead of `values.yaml`) would not be excluded, which would potentially expose confidential data in bundle resources. Helm values files are now excluded from bundle resources regardless of how you reference them.	28 Aug 2025	Rancher v2.12.1, v2.11.5 and v2.10.9
CVE-2025-23390	This vulnerability only affects customers using Continuous Delivery with Fleet where Fleet does not validate a server’s certificate when connecting through SSH. This can allow for a main-in-the-middle-attack against Fleet. The fix provides a new `insecureSkipHostKeyChecks` value for the `fleet` Helm chart. The default value is set to `true` (opt-in) for Rancher v2.9 - v2.11 for backward compatibility. The default value is set to `false` (opt-out) for Rancher v2.12 and later, and Fleet v0.13 and later. `true` (opt-in): If `insecureSkipHostKeyChecks` is set to `true`, then not finding any matching `known_hosts` entry for an SSH host will not lead to any error. Please note, regardless of the configuration setting, if the `known-hosts` ConfigMap is deleted it will lead to errors as it will be considered a symptom of an incomplete Fleet deployment. `false` (opt-out): If `insecureSkipHostKeyChecks` is set to `false`, then strict host key checks are enabled. When enabled, the checks ensure that when using SSH, Fleet rejects connection attempts to hosts not matching any entry found in (decreasing order of precedence): A secret referenced by name in a `GitRepo` which is located in the same `GitRepo’s` namespace. If no such secret name is provided, in a `gitcredential` secret located in the same namespace. A new `known-hosts` ConfigMap, created during the Fleet chart installation time and located in the namespace `cattle-fleet-system`. This happens regardless of whether a `GitRepo` uses an SSH URL to point to a Git repository since, once cloned, a repository may be found to contain external resources to be retrieved, such as Helm artifacts. A limitation with the default `known_hosts` entries is that they are only provided for GitHub, Gitlab, Bitbucket and Azure DevOps hosts. If you need to connect to a different host, or if key fingerprints for the provided entries are updated, the following options are available: Manually update the default `known-hosts` ConfigMap. Reference a secret from your `GitRepo` resources, containing the updated or additional `known_hosts` entries. Create a `gitcredential` secret containing the entries for `GitRepo` resources that do not already reference a secret.	24 Apr 2025	Rancher v2.11.1, v2.10.5, and v2.9.9
CVE-2024-22031	A vulnerability was found where users could create a project and then gain access to arbitrary projects. As a fix, a new field has been added to projects called the `BackingNampespace`, which represents the namespace created for a project containing all resources needed for project operations. This includes resources such as ProjectRoleTemplateBindings, project-scoped secrets and workloads. The field is populated automatically during project creation and is formatted as `<clusterID>-<project.Name>`. For example, if your project is named `project-abc123` in a cluster with ID `cluster-xyz789`, then the project will have the `BackingNampespace`: `cluster-xyz789-project-abc123`. Existing projects will not be migrated and only newly created projects will have the new namespace naming convention.	24 Apr 2025	Rancher v2.11.1, v2.10.5, and v2.9.9
CVE-2023-32198	A vulnerability was found where users with permission to create a service in the Kubernetes cluster where Rancher is deployed can take over the Rancher UI, display their own UI, and gather sensitive information. This is only possible when the setting `ui-offline-preferred` is set to `remote`. This release introduces a patch, and the malicious user can no longer serve their own UI. If users can’t upgrade, please make sure that only trustable users have access to create a service in the local cluster.	24 Apr 2025	Rancher v2.11.1, v2.10.5, v2.9.9, and v2.8.15
CVE-2025-23391	A vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts. A Restricted Administrator should not be allowed to change the password of more privileged users unless it contains the Manage Users permissions. A new validation has been added to block a user from editing or deleting another user with more permissions than themselves. Rancher deployments where the Restricted Administrator role is not being used are not affected by this CVE.	31 Mar 2025	Rancher v2.11.0, v2.10.4, v2.9.8 and v2.8.14

CVE-2026-75036

Fixed a vulnerability in Fleet’s Helm template preprocessing where untrusted bundle content could cause the Fleet controller to disclose cluster metadata and information about hosts reachable from the controller.

26 August 2026

Fleet v0.16.1, Fleet v0.15.6, Fleet v0.14.10, Fleet v0.13.15, Fleet v0.12.19

CVE-2026-55998

Fixed a security vulnerability in Rancher’s unauthenticated cluster import endpoint where an attacker could enumerate valid cluster IDs and detect private registry usage by observing distinguishable HTTP response codes.

30 July 2026

Rancher v2.14.4, Rancher v2.13.8, Rancher v2.12.12, and Rancher v2.11.16.

CVE-2026-55996

Fixed a security vulnerability where an unauthenticated attacker with cluster-internal network access could flood TLS listeners in cattle-cluster-agent and in the Rancher server with requests containing arbitrary hostnames, causing serving certificates to accumulate excessive Subject Alternative Names (SANs) until TLS handshakes failed. The fix applies CN filtering to reject attacker-supplied SNI hostnames and caps the maximum number of SANs per certificate.

30 July 2026

Rancher v2.14.4, Rancher v2.13.8, Rancher v2.12.12, and Rancher v2.11.16.

CVE-2026-44945

Fixed a critical security vulnerability in Rancher’s impersonation middleware (pkg/auth/requests/impersonate.go) where an authenticated user with the default user global role could exploit a cross-cluster impersonation flaw to impersonate privileged identities, including system:masters, against the local Rancher management cluster. This allowed full administrative takeover of the Rancher control plane and all managed downstream clusters and secrets.

30 July 2026

Rancher v2.14.4, Rancher v2.13.8, Rancher v2.12.12, and Rancher v2.11.16.

CVE-2026-44949

Fixed a security vulnerability in rancher-webhook where the FleetWorkspace mutating admission webhook performed side effects without authenticating requests, allowing a pod inside the cluster to create arbitrary namespaces and inject RBAC bindings.

29 June 2026

Rancher v2.14.3, Rancher v2.13.7, Rancher v2.12.11 and Rancher v2.11.15

CVE-2026-44946

Fixed a security vulnerability in Rancher’s SAML authentication handler where a valid signed SAML response could be replayed by an attacker who had also captured the victim’s pre-authentication SAML state cookie, allowing the attacker to create a separate authenticated session with the victim’s permissions. All SAML providers (Okta, Ping, ADFS, Keycloak, Shibboleth) were affected.

29 June 2026

Rancher v2.14.3, Rancher v2.13.7, Rancher v2.12.11 and Rancher v2.11.15

CVE-2026-44939

Rancher now validates the authImage parameter in cluster import manifests to prevent YAML injection attacks.

27 May 2026

Rancher v2.14.2, Rancher v2.13.6, v2.12.10, v2.11.14, and v2.10.12

CVE-2026-25705

Rancher now protects against arbitrary file access via path traversal in Rancher Extensions. Note by default only users with administrative permissions can deploy UI extensions unless explicit permission is granted to other users.

30 Apr 2026

Rancher v2.14.1, v2.13.5, v2.12.9, and v2.11.13

CVE-2025-62879

Rancher now provides new versions of the Rancher Backup chart which prevent the leak of secret S3 credentials via the Rancher Backup pod log.

29 Jan 2026

Rancher v2.13.2, v2.12.6, v2.11.10, and v2.10.11

CVE-2025-67601

Rancher now removes the ability to fetch CA certificates stored in Rancher’s setting cacerts when using the login command.

29 Jan 2026

Rancher v2.13.2, v2.12.6, v2.11.10, and v2.10.11

CVE-2023-32199

Rancher now removes the corresponding ClusterRoleBindings whenever the admin GlobalRole or its GlobalRoleBindings are deleted. Previously orphaned ClusterRoleBindings were marked with the annotation authz.cluster.cattle.io/admin-globalrole-missing=true.

23 Oct 2025

Rancher v2.12.3 and v2.11.7

CVE-2024-58260

Setting the username of one user as the same username of another user causes an error when either user attempts to log in. Therefore, a user with the Manage Users permission could potentially deny any user, including admins, from logging in. To prevent this, usernames have been made immutable once set, and it is not possible to update or create a user with a username that is already in use.

25 Sep 2025

Rancher v2.12.2, v2.11.6, v2.10.10, and v2.9.12

CVE-2024-58267

The Rancher CLI is modified to print the requestId more visibly than as part of the login URL. It also adds a cli=true origin marker to the URL. The dashboard is modified to recognize the presence of the requestId and uses that to show a warning message to the user, asking for verification that they initiated a CLI login with the related Id. The non-presence of the origin marker enables the dashboard to distinguish between the modified CLI and older CLI’s, and adjust the message accordingly.

25 Sep 2025

Rancher v2.12.2, v2.11.6, v2.10.10, and v2.9.12

CVE-2025-54468

Impersonate-* headers are removed for requests made through the /meta/proxy Rancher endpoint (e.g. when cloud credentials are being created) as the headers may contain identifiable and/or sensitive information.

25 Sep 2025

Rancher v2.12.2, v2.11.6, v2.10.10, and v2.9.12

CVE-2024-58259

POSTs to the Rancher API endpoints are now limited to 1 Mi; this is configurable through the settings if you need a larger limit. The Rancher authentication endpoints are configured independently of the main public API (as you might need bigger payloads in the other API endpoints). Suppose you need to increase the maximum allowed payload for authentication. In that case, you can set the environment variable CATTLE_AUTH_API_BODY_LIMIT to a quantity, e.g., 2 Mi, which would allow larger payloads for the authentication endpoints.

28 Aug 2025

Rancher v2.12.1, v2.11.5, v2.10.9 and v2.9.11

CVE-2024-52284

Following a recent change excluding Helm values files from bundles, an edge case subsisted where the values files referenced in fleet.yaml with your directory name (e.g., my-dir/values.yaml instead of values.yaml) would not be excluded, which would potentially expose confidential data in bundle resources. Helm values files are now excluded from bundle resources regardless of how you reference them.

28 Aug 2025

Rancher v2.12.1, v2.11.5 and v2.10.9

CVE-2025-23390

This vulnerability only affects customers using Continuous Delivery with Fleet where Fleet does not validate a server’s certificate when connecting through SSH. This can allow for a main-in-the-middle-attack against Fleet. The fix provides a new insecureSkipHostKeyChecks value for the fleet Helm chart. The default value is set to true (opt-in) for Rancher v2.9 - v2.11 for backward compatibility. The default value is set to false (opt-out) for Rancher v2.12 and later, and Fleet v0.13 and later.

true (opt-in):

If insecureSkipHostKeyChecks is set to true, then not finding any matching known_hosts entry for an SSH host will not lead to any error. Please note, regardless of the configuration setting, if the known-hosts ConfigMap is deleted it will lead to errors as it will be considered a symptom of an incomplete Fleet deployment.

false (opt-out):

If insecureSkipHostKeyChecks is set to false, then strict host key checks are enabled. When enabled, the checks ensure that when using SSH, Fleet rejects connection attempts to hosts not matching any entry found in (decreasing order of precedence):

A secret referenced by name in a GitRepo which is located in the same GitRepo’s namespace.
If no such secret name is provided, in a gitcredential secret located in the same namespace.
A new known-hosts ConfigMap, created during the Fleet chart installation time and located in the namespace cattle-fleet-system.

This happens regardless of whether a GitRepo uses an SSH URL to point to a Git repository since, once cloned, a repository may be found to contain external resources to be retrieved, such as Helm artifacts.

A limitation with the default known_hosts entries is that they are only provided for GitHub, Gitlab, Bitbucket and Azure DevOps hosts. If you need to connect to a different host, or if key fingerprints for the provided entries are updated, the following options are available:

Manually update the default known-hosts ConfigMap.
Reference a secret from your GitRepo resources, containing the updated or additional known_hosts entries.
Create a gitcredential secret containing the entries for GitRepo resources that do not already reference a secret.

24 Apr 2025

Rancher v2.11.1, v2.10.5, and v2.9.9

CVE-2024-22031

A vulnerability was found where users could create a project and then gain access to arbitrary projects. As a fix, a new field has been added to projects called the BackingNampespace, which represents the namespace created for a project containing all resources needed for project operations. This includes resources such as ProjectRoleTemplateBindings, project-scoped secrets and workloads.

The field is populated automatically during project creation and is formatted as <clusterID>-<project.Name>. For example, if your project is named project-abc123 in a cluster with ID cluster-xyz789, then the project will have the BackingNampespace: cluster-xyz789-project-abc123. Existing projects will not be migrated and only newly created projects will have the new namespace naming convention.

24 Apr 2025

Rancher v2.11.1, v2.10.5, and v2.9.9

CVE-2023-32198

A vulnerability was found where users with permission to create a service in the Kubernetes cluster where Rancher is deployed can take over the Rancher UI, display their own UI, and gather sensitive information. This is only possible when the setting ui-offline-preferred is set to remote. This release introduces a patch, and the malicious user can no longer serve their own UI. If users can’t upgrade, please make sure that only trustable users have access to create a service in the local cluster.

24 Apr 2025

Rancher v2.11.1, v2.10.5, v2.9.9, and v2.8.15

CVE-2025-23391

A vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts. A Restricted Administrator should not be allowed to change the password of more privileged users unless it contains the Manage Users permissions. A new validation has been added to block a user from editing or deleting another user with more permissions than themselves. Rancher deployments where the Restricted Administrator role is not being used are not affected by this CVE.

31 Mar 2025

Rancher v2.11.0, v2.10.4, v2.9.8 and v2.8.14