Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:34 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Exact source revision recorded 24 Oct 2026 13:19:41 UTC. It does not establish the source's current position. Latest evidence.

osv · GHSA-mjcp-rj3c-36fr

Published

### 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](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

Source published
26 Sep 2025 13:02:38 UTC
Source modified
10 Sep 2026 03:50:28 UTC
Observed here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 10 Nov 11:34 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current