Skip to content

Rancher sends sensitive information to external services through the `/meta/proxy` endpoint

Moderate severity GitHub Reviewed Published Sep 25, 2025 in rancher/rancher

Package

gomod github.com/rancher/rancher (Go)

Affected versions

>= 2.12.0, < 2.12.2
>= 2.11.0, < 2.11.6
>= 2.10.0, < 2.10.10
>= 2.9.0, < 2.9.12

Patched versions

2.12.2
2.11.6
2.10.10
2.9.12

Description

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:

References

@samjustus samjustus published to rancher/rancher Sep 25, 2025
Published to the GitHub Advisory Database Sep 26, 2025
Reviewed Sep 26, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

EPSS score

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

CVE ID

CVE-2025-54468

GHSA ID

GHSA-mjcp-rj3c-36fr

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.