How severe is GHSA-mjcp-rj3c-36fr?

GHSA-mjcp-rj3c-36fr has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-mjcp-rj3c-36fr?

GHSA-mjcp-rj3c-36fr affects the following packages: github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go). Ecosystems affected: Go.

How do I fix GHSA-mjcp-rj3c-36fr?

Update github.com/rancher/rancher to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjcp-rj3c-36fr is resolved across your whole dependency graph.

How do I detect GHSA-mjcp-rj3c-36fr in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mjcp-rj3c-36fr if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-mjcp-rj3c-36fr actively exploited in the wild?

No public exploit code has been indexed for GHSA-mjcp-rj3c-36fr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mjcp-rj3c-36fr?

GHSA-mjcp-rj3c-36fr has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mjcp-rj3c-36fr?

GHSA-mjcp-rj3c-36fr is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mjcp-rj3c-36fr published, and has it been updated?

GHSA-mjcp-rj3c-36fr was published on September 26, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Rancher sends sensitive information to external services through the `/meta/proxy` endpointGHSA-mjcp-rj3c-36fr

MEDIUM

GHSA-mjcp-rj3c-36fr is a medium-severity (CVSS 4.7) Information Exposure vulnerability in github.com/rancher/rancher. A fix is available for github.com/rancher/rancher — see the affected versions and patch details below.

Also known asCVE-2025-54468GO-2025-3982

Published

Sep 26, 2025

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mjcp-rj3c-36fr.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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:

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rancher/rancher`	≥ 2.12.0&&< 2.12.2	2.12.2`go get github.com/rancher/rancher@v2.12.2`
🐹Go	`github.com/rancher/rancher`	≥ 2.11.0&&< 2.11.6	2.11.6`go get github.com/rancher/rancher@v2.11.6`
🐹Go	`github.com/rancher/rancher`	≥ 2.10.0&&< 2.10.10	2.10.10`go get github.com/rancher/rancher@v2.10.10`
🐹Go	`github.com/rancher/rancher`	≥ 2.9.0&&< 2.9.12	2.9.12`go get github.com/rancher/rancher@v2.9.12`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/rancher/rancher to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjcp-rj3c-36fr is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### 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`, i

O3 Security · Impact-Aware SCA

Is GHSA-mjcp-rj3c-36fr in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 26, 2025

Last updated

Sep 10, 2026

Identifiers

GHSA-mjcp-rj3c-36fr

GO-2025-3982

References

Advisorynvd.nist.gov · CVE 2025 54468 Webgithub.com · GHSA mjcp rj3c 36fr Webbugzilla.suse.com · show bug.cgi Webpkg.go.dev · GO 2025 3982 Packagegithub.com · rancher

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting rancher are rated as high or higher (top: critical).

CVE-2026-41053CVE-2026-44939CVE-2026-41052CVE-2026-25705CVE-2022-31247CVE-2021-36783CVE-2021-25320GHSA-hwm2-4ph6-w6m5

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

Rancher sends sensitive information to external services through the `/meta/proxy` endpointGHSA-mjcp-rj3c-36fr

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-mjcp-rj3c-36fr in your dependencies?