# CVE-2025-54468: Rancher sends sensitive information to external services through the `/meta/proxy` endpoint

> Rancher Manager leaks sensitive user information, such as email addresses, to external services via the /meta/proxy endpoint.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Oct 2025
- **Updated:** 2 Oct 2025
- **Also known as:** GHSA-mjcp-rj3c-36fr, GO-2025-3982

## What is CVE-2025-54468?

CVE-2025-54468 is a medium-severity vulnerability in SUSE rancher, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-54468?

9 open source packages ship an affected version, including github.com/rancher/rancher.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/rancher` | Go | All versions | None |
| `github.com/rancher/rancher` | Go | From 2.10.0 | 2.10.10 |
| `github.com/rancher/rancher` | Go | From 2.10.0 | 2.10.10 |
| `github.com/rancher/rancher` | Go | From 2.11.0 | 2.11.6 |
| `github.com/rancher/rancher` | Go | From 2.11.0 | 2.11.6 |
| `github.com/rancher/rancher` | Go | From 2.12.0 | 2.12.2 |
| `github.com/rancher/rancher` | Go | From 2.12.0 | 2.12.2 |
| `github.com/rancher/rancher` | Go | From 2.9.0 | 2.9.12 |
| `github.com/rancher/rancher` | Go | From 2.9.0 | 2.9.12 |

## How do I fix CVE-2025-54468?

Upgrade github.com/rancher/rancher to a fixed version for your release line: 2.10.10, 2.11.6, 2.12.2 or 2.9.12.

## Is CVE-2025-54468 being exploited?

There is no known exploitation of CVE-2025-54468 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54468 and fix it if it is affected.

What it is: CVE-2025-54468 is a medium-severity vulnerability in SUSE rancher, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-54468 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/rancher (Go): affected all versions; no fix listed
- github.com/rancher/rancher (Go): affected from 2.10.0; fixed in 2.10.10
- github.com/rancher/rancher (Go): affected from 2.10.0; fixed in 2.10.10
- github.com/rancher/rancher (Go): affected from 2.11.0; fixed in 2.11.6
- github.com/rancher/rancher (Go): affected from 2.11.0; fixed in 2.11.6
- github.com/rancher/rancher (Go): affected from 2.12.0; fixed in 2.12.2
- github.com/rancher/rancher (Go): affected from 2.12.0; fixed in 2.12.2
- github.com/rancher/rancher (Go): affected from 2.9.0; fixed in 2.9.12
- github.com/rancher/rancher (Go): affected from 2.9.0; fixed in 2.9.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54468/ (Markdown: https://insights.sbomify.com/CVE-2025-54468/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54468
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54468
- OSV: https://osv.dev/vulnerability/CVE-2025-54468

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54468/
Summaries are generated and may contain mistakes; the official description above is the record.