Public mode

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

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Rancher CLI SAML authentication is vulnerable to phishing attacks

CVSS 3.1 8.0 HIGHEUVD CVSS 3.1 8.0 CVSS 3.1 · [email protected] · Secondary 8.0 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/rancher/rancher 2.12.2Fixed by github.com/rancher/rancher 2.11.6Fixed by github.com/rancher/rancher 2.10.10Fixed by github.com/rancher/rancher 2.9.12osv · severity unknownKEV status unknown

cve-program · CVE-2024-58267

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-31336

Published

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.

Read the publisher's advisory

nvd · CVE-2024-58267

Published

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.

Read the publisher's advisory

osv · GHSA-v3vj-5868-2ch2

Published

### 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](https://attack.mitre.org/tactics/TA0004/) 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: 1. The Rancher CLI now reports the `requestId` that 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. 2. 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](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/).

Read the publisher's advisory

osv · GO-2025-3984

Published

Rancher CLI SAML authentication is vulnerable to phishing attacks in github.com/rancher/rancher. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/rancher/rancher from v2.9.0 before v2.9.12, from v2.10.0 before v2.10.10, from v2.11.0 before v2.11.6, from v2.12.0 before v2.12.2.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-58267

Published

github.com/rancher/rancher

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "packageName": "github.com/rancher/rancher",
                    "product": "rancher",
                    "vendor": "SUSE",
                    "versions": [
                        {
                            "lessThan": "2.12.2",
                            "status": "affected",
                            "version": "2.12.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.11.6",
                            "status": "affected",
                            "version": "2.11.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.10.10",
                            "status": "affected",
                            "version": "2.10.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.9.12",
                            "status": "affected",
                            "version": "2.9.0",
                            "versionType": "semver"
                        }
                    ]
                }

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

euvd · EUVD-2025-31336

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 2, 2025, 12:08:30 PM

dateUpdated: Feb 26, 2026, 5:48:22 PM

2 related source bulletins · separate from aliases

WID-SEC-W-2025-2141: Rancher: Mehrere Schwachstellen

CVE-2024-58260 · CVE-2024-58267 · CVE-2025-54468

openSUSE-SU-2025:15666-1: govulncheck-vulndb-0.0.20251023T162509-1.1 on GA media

CVE-2024-58260 · CVE-2024-58267 · CVE-2025-23266 · CVE-2025-23267 · CVE-2025-54468 · CVE-2025-55191 · CVE-2025-59163 · CVE-2025-59531 · CVE-2025-59537 · CVE-2025-59538 · CVE-2025-59823 · CVE-2025-59824 · CVE-2025-59941 · CVE-2025-59942 · CVE-2025-59956 · CVE-2025-61595 · CVE-2025-61926

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

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

nvd · CVE-2024-58267

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-345

Original publisher date fields

published: 2025-10-02T12:15:28.773

lastModified: 2026-06-17T08:14:44.730

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

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

osv · GHSA-v3vj-5868-2ch2

Published

github.com/rancher/rancher

Go

SEMVER · introduced 2.12.0 → fixed 2.12.2

github.com/rancher/rancher

Go

SEMVER · introduced 2.11.0 → fixed 2.11.6

github.com/rancher/rancher

Go

SEMVER · introduced 2.10.0 → fixed 2.10.10

github.com/rancher/rancher

Go

SEMVER · introduced 2.9.0 → fixed 2.9.12

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

osv · GO-2025-3984

Published

github.com/rancher/rancher

Go

SEMVER · introduced 0

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

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 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current