# CVE-2024-58267: Rancher CLI SAML authentication is vulnerable to phishing attacks > Attackers can steal Rancher authentication tokens via phishing due to a flawed SAML protocol in the CLI, leading to account takeover. - **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 2 Oct 2025 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-v3vj-5868-2ch2, GO-2025-3984 ## What is CVE-2024-58267? CVE-2024-58267 is a high-severity vulnerability in SUSE rancher, published on 2 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2024-58267? 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-2024-58267? 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-2024-58267 being exploited? There is no known exploitation of CVE-2024-58267 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-58267 and fix it if it is affected. What it is: CVE-2024-58267 is a high-severity vulnerability in SUSE rancher, published on 2 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-58267 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-2024-58267/ (Markdown: https://insights.sbomify.com/CVE-2024-58267/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58267 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58267 - OSV: https://osv.dev/vulnerability/CVE-2024-58267 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-58267/ Summaries are generated and may contain mistakes; the official description above is the record.