Skip to content
Fencer Intel
medium 4.7

CVE-2025-54468 json

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

published last yr. modified 28d ago also GHSA-mjcp-rj3c-36fr , GO-2025-3982 , EUVD-2025-31337

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/rancher/rancher 2.9.12, 2.10.10, 2.11.6, 2.12.2
  • SUSE rancher 2.9.12, 2.10.10, 2.11.6, 2.12.2
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20251023T162509-150000.1.110.1

suse advisories SUSE-SU-2025:3799-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20251023T162509-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15666-1

Is CVE-2025-54468 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
GitHub 3.1 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/rancher/rancher
>=2.12.0, <2.12.2
>=2.11.0, <2.11.6
>=2.10.0, <2.10.10
>=2.9.0, <2.9.12
all versions
2.12.2
2.11.6
2.10.10
2.9.12

Affected products

  • SUSE rancher

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.