CVE-2024-58267 json
Rancher CLI SAML authentication is vulnerable to phishing attacks
published 2025-09-26 13 mo ago modified 2026-09-10 1 mo ago also GHSA-v3vj-5868-2ch2 , GO-2025-3984 , EUVD-2025-31336
- cvss
- 8.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 13 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H |
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-345 Insufficient Verification of Data Authenticity
References
Sources
- CVE List CVE-2024-58267
- GitHub Advisory GHSA-v3vj-5868-2ch2
- NVD CVE-2024-58267
- OSV GO-2025-3984
Fencer Vulns 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.