CVE-2025-54468 is a medium-severity security vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.12.0, < 2.12.2. It is fixed in 2.12.2, 2.11.6, 2.10.10, 2.9.12.
Impact A vulnerability has been identified within Rancher Manager whereby Impersonate-Extra- headers are being sent to an external entity, for example amazonaws.com, via the /meta/proxy Rancher endpoint. These headers may contain identifiable and/or sensitive information e.g. email addresses. If the authentication provider is configured to have email or other sensitive and/or identifiable information as part of the username and principal ID then when a new cloud credential is being created in Rancher Manager this information is sent to an external entity such as amazonaws.com, in case of an AWS cloud credentials, in Impersonate-Extra-Username and/or Impersonate-Extra-Principalid headers. Please note that neither password, password hashes or Rancher’s related authentication tokens are leaked in those requests. The entities to which such information is sent to are limited by the whitelisted domains specified in nodedrivers.management.cattle.io objects. For example, the Amazon EC2 node driver contains the following whitelisted domains: iam.amazonaws.com iam.us-gov.amazonaws.com iam.%.amazonaws.com.cn iam.global.api.aws ec2.%.amazonaws.com ec2.%.amazonaws.com.cn ec2.%.api.aws eks.%.amazonaws.com eks.%.amazonaws.com.cn eks.%.api.aws kms.%.amazonaws.com kms.%.amazonaws.com.cn kms.%.api.aws While the DigitalOcean driver contains the following whitelisted domain: api.digitalocean.com Patches This vulnerability is addressed by filtering all Impersonate- headers from the original request by the /meta/proxy endpoint. Patched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10, and v2.9.12. Workarounds There are no known workarounds for this issue. References If you have any questions or comments about this advisory: Reach out to the SUSE Rancher Security team for security related inquiries. Open an issue in the Rancher repository. Verify with our support matrix and product support lifecycle.
CVE-2025-54468 has a CVSS score of 4.7 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.12.2, 2.11.6, 2.10.10, 2.9.12). Upgrading removes the vulnerable code path.
go
github.com/rancher/rancher (>= 2.12.0, < 2.12.2)github.com/rancher/rancher (>= 2.11.0, < 2.11.6)github.com/rancher/rancher (>= 2.10.0, < 2.10.10)github.com/rancher/rancher (>= 2.9.0, < 2.9.12)github.com/rancher/rancher → 2.12.2 (go)github.com/rancher/rancher → 2.11.6 (go)github.com/rancher/rancher → 2.10.10 (go)github.com/rancher/rancher → 2.9.12 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2025-54468 is reachable in your applications. Explore open-source security for your team.
See if CVE-2025-54468 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2025-54468 in your environment →Upgrade the following packages to resolve this vulnerability:
github.com/rancher/rancher to 2.12.2 or latergithub.com/rancher/rancher to 2.11.6 or latergithub.com/rancher/rancher to 2.10.10 or latergithub.com/rancher/rancher to 2.9.12 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2025-54468 is a medium-severity security vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.12.0, < 2.12.2. It is fixed in 2.12.2, 2.11.6, 2.10.10, 2.9.12.
CVE-2025-54468 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/rancher/rancher (go) versions >= 2.12.0, < 2.12.2 is affected.
Yes. CVE-2025-54468 is fixed in 2.12.2, 2.11.6, 2.10.10, 2.9.12. Upgrade to this version or later.
Whether CVE-2025-54468 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
github.com/rancher/rancher to 2.12.2 or latergithub.com/rancher/rancher to 2.11.6 or latergithub.com/rancher/rancher to 2.10.10 or latergithub.com/rancher/rancher to 2.9.12 or later