GHSA-v3vj-5868-2ch2
HIGHGHSA-v3vj-5868-2ch2 is a high-severity (CVSS 8) CWE-345 vulnerability in github.com/rancher/rancher. O3 Security confirms whether GHSA-v3vj-5868-2ch2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Rancher CLI SAML authentication is vulnerable to phishing attacks
Real-World Exposure
github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancherReal-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 the SAML authentication from the Rancher CLI tool is vulnerable to phishing attacks. The custom authentication protocol for SAML-based providers can be abused to steal Rancher’s authentication tokens.
Rancher Manager deployments without SAML authentication enabled are not affected by this vulnerability.
An attacker can generate a phishing SAML login URL which contains a publicKey and requestId controlled by the attacker. The attacker can then give the link to another user (eg: admin) and if the victim goes to the link unsuspectingly, they might not notice the bad parameters in the URL. The user will be prompted to login and might believe that its session has ended so they need to re-login. By clicking on the link, they will be logged in and an encrypted token will be created with the attacker's public key. The attacker can then decrypt the victim’s Rancher token, enabling the attack
Please consult the associated MITRE ATTACK Techniques - Privilege Escalation for further information about this category of attack.
Patches
This vulnerability is addressed by changes in both Rancher Manager and the CLI. The fixed versions:
- The Rancher CLI now reports the
requestIdthat is relevant to the authentication session in process as a separate message to the terminal, making it easier for the user to identify and compare. - The Rancher login page for SAML authentication will display a suitable warning to ensure that the user seeing the login page is aware of the login process with the related
requestId, enabling users to verify whether the request was intended or not.
Patched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10, and v2.9.12.
Workarounds
If you cannot update to one of the fixed versions, make sure to check the URL printed by the Rancher CLI when performing a SAML authentication flow, especially the requestId parameter. The URL and the requestId printed by the CLI must be the same URL that you access and see when finalizing the SAML authentication flow in your browser for the Rancher UI. The URL has the format:
<rancher_ui_address>/dashboard/auth/login?requestId=<requestid>&publicKey=<pubkey>&responseType=<responsetype>
If the URL presented in the browser is different from the one logged by the CLI, the user must not proceed with the login, as they might be under a phishing attack.
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/rancher/rancher | ≥ 2.12.0&&< 2.12.2 | 2.12.2 |
| 🐹Go | github.com/rancher/rancher | ≥ 2.11.0&&< 2.11.6 | 2.11.6 |
| 🐹Go | github.com/rancher/rancher | ≥ 2.10.0&&< 2.10.10 | 2.10.10 |
| 🐹Go | github.com/rancher/rancher | ≥ 2.9.0&&< 2.9.12 | 2.9.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-v3vj-5868-2ch2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v3vj-5868-2ch2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-v3vj-5868-2ch2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v3vj-5868-2ch2 in your dependencies?
O3 detects GHSA-v3vj-5868-2ch2 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.