Every CVE Search/ Get API key

CVE-2024-58267

Rancher CLI SAML authentication is vulnerable to phishing attacks

8.0 HighFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
High
Privileges needed
Low
User interaction
Required

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

Exploit likelihood

0.24%Up 0.2 points since Oct 3, 2025
90%50%10%1%

What each source reports

CVE List Score used 8.0

Rancher CLI SAML authentication is vulnerable to phishing attacks

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.

Record
CVE-2024-58267
CVSS 3.1
8.0 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-345
Updated
2026-11-02
EUVDEUVD-2025-31336 8.0

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.

Record
EUVD-2025-31336
CVSS 3.1
8.0 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-v3vj-5868-2ch2 8.0

Rancher CLI SAML authentication is vulnerable to phishing attacks

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:

  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:

Record
GHSA-v3vj-5868-2ch2
CVSS 3.1
8.0 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-345
Updated
2026-11-02
NVD 8.0

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.

Record
CVE-2024-58267
CVSS 3.1
8.0 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-345
Updated
2026-11-02
OSV 8.0

Rancher CLI SAML authentication is vulnerable to phishing attacks

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.

Record
CVE-2024-58267
CVSS 3.1
8.0 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-345
Updated
2026-11-02
OSVGHSA-v3vj-5868-2ch2 8.0

Rancher CLI SAML authentication is vulnerable to phishing attacks

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:

  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:

Record
GHSA-v3vj-5868-2ch2
CVSS 3.1
8.0 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Weakness
CWE-345
Updated
2026-11-02
Show 4 moreShow less
OSVGO-2025-3984 No score

Rancher CLI SAML authentication is vulnerable to phishing attacks in github.com/rancher/rancher

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.

Record
GO-2025-3984
Updated
2026-11-02
OSVopenSUSE-SU-2025:15666-1 No score

govulncheck-vulndb-0.0.20251023T162509-1.1 on GA media

These are all security issues fixed in the govulncheck-vulndb-0.0.20251023T162509-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15666-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
  • GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
  • GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
  • GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
  • GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
  • GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
  • GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
  • GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
  • GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
  • GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
  • GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
  • GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
  • GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
  • GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
  • GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
  • GO-2026-5933 GHSA-3g4q-2f67-2gvh
  • GO-2026-5934 GHSA-59qp-cfj3-rp64
  • GO-2026-5935 GHSA-7856-g3gv-9wq8
  • GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
  • GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
  • GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
  • GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
  • GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
  • GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
  • GO-2026-5942 CVE-2026-46600
  • GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
  • GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
  • GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
  • GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
  • GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
  • GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
  • GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
  • GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
  • GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
  • GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
  • GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
  • GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
  • GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
  • GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
  • GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
  • GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
  • GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
  • GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
  • GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
  • GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
  • GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
  • GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
  • GO-2026-5969 GHSA-g936-7jqj-mwv8
  • GO-2026-5970 CVE-2026-56852
  • GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
  • GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
  • GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
  • GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
  • GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
  • GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
  • GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
  • GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
  • GO-2026-5981 GHSA-mqxv-9rm6-w8qc
  • GO-2026-5982 GHSA-pqg7-v6wh-3pfp
  • GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
  • GO-2026-5985 GHSA-7rx3-5wx3-5v76
  • GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
  • GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
  • GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
  • GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
  • GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
  • GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
  • GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
  • GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
  • GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
  • GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
  • GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
  • GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
  • GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
  • GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
  • GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
  • GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
Record
openSUSE-SU-2026:21483-1
Updated
2026-11-02
OSVSUSE-SU-2025:3799-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20251023T162509 2025-10-23T16:25:09Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3979 CVE-2025-59824 GHSA-hqrf-67pm-wgfq
    • GO-2025-3981 CVE-2025-59823 GHSA-227x-7mh8-3cf6
    • GO-2025-3982 CVE-2025-54468 GHSA-mjcp-rj3c-36fr
    • GO-2025-3983 CVE-2024-58260 GHSA-q82v-h4rq-5c86
    • GO-2025-3984 CVE-2024-58267 GHSA-v3vj-5868-2ch2
    • GO-2025-3985 GHSA-q6hv-wcjr-wp8h
    • GO-2025-3986 CVE-2025-59163 GHSA-6q9c-m9fr-865m
    • GO-2025-3989 CVE-2025-59941 GHSA-7pq9-rf9p-wcrf
    • GO-2025-3990 CVE-2025-59942 GHSA-g99p-47x7-mq88
    • GO-2025-3991 CVE-2025-59956 GHSA-w64r-2g3w-w8w4
    • GO-2025-3992 CVE-2025-23266 GHSA-vmg3-7v43-9g23
    • GO-2025-3993 CVE-2025-59531 GHSA-f9gq-prrc-hrhc
    • GO-2025-3994 CVE-2025-55191 GHSA-g88p-r42r-ppp9
    • GO-2025-3995 CVE-2025-59538 GHSA-gpx4-37g2-c8pv
    • GO-2025-3996 CVE-2025-59537 GHSA-wp4p-9pxh-cgx2
    • GO-2025-3997 CVE-2025-61595 GHSA-qwvm-wqq8-8j69
    • GO-2025-3998 CVE-2025-23267 GHSA-67jc-hmvg-q4c7
    • GO-2025-4018 CVE-2025-61926 GHSA-33f4-mjch-7fpr
    • GO-2025-4019 GHSA-xc79-566c-j4qx

  • Update to version 0.0.20250924T192141 2025-09-24T19:21:41Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3962 CVE-2025-59341 GHSA-49pv-gwxp-532r
    • GO-2025-3963 CVE-2025-59348 GHSA-2qgr-gfvj-qpcr
    • GO-2025-3964 CVE-2025-59349 GHSA-8425-8r2f-mrv6
    • GO-2025-3965 CVE-2025-59345 GHSA-89vc-vf32-ch59
    • GO-2025-3966 CVE-2025-59347 GHSA-98x5-jw98-6c97
    • GO-2025-3967 CVE-2025-59342 GHSA-g2h5-cvvr-7gmw
    • GO-2025-3968 CVE-2025-59346 GHSA-g2rq-jv54-wcpr
    • GO-2025-3969 CVE-2025-59353 GHSA-255v-qv84-29p5
    • GO-2025-3970 CVE-2025-59351 GHSA-4mhv-8rh3-4ghw
    • GO-2025-3971 CVE-2025-59352 GHSA-79hx-3fp8-hj66
    • GO-2025-3972 CVE-2025-59350 GHSA-c2fc-9q9c-5486
    • GO-2025-3973 CVE-2025-59354 GHSA-hx2h-vjw2-8r54
    • GO-2025-3974 CVE-2025-59410 GHSA-mcvp-rpgg-9273
    • GO-2025-3976 CVE-2025-10630 GHSA-g4rr-88fc-26fj
    • GO-2025-3977 CVE-2025-9079 GHSA-qx3f-6vq3-8j8m
    • GO-2025-3978 CVE-2025-9081 GHSA-f72g-52v7-mg3p

  • Update to version 0.0.20250922T204835 2025-09-22T20:48:35Z (jsc#PED-11136).

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3955 CVE-2025-47910 CVE-2025-47910
Record
SUSE-SU-2025:3799-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/rancher/rancher
Go
 2.12.0 up to 2.12.2
2.12.2
github.com/rancher/rancher
Go
 2.11.0 up to 2.11.6
2.11.6
github.com/rancher/rancher
Go
 2.10.0 up to 2.10.10
2.10.10
github.com/rancher/rancher
Go
 2.9.0 up to 2.9.12
2.9.12
github.com/rancher/rancher
Go
 All versions None known
govulncheck-vulndb
SUSE:Linux Enterprise Module for Package Hub 15 SP6
From an advisory covering 34 CVEs
 before 0.0.20251023T162509-150000.1.110.1
0.0.20251023T162509-150000.1.110.1
govulncheck-vulndb
openSUSE:Leap 15.6
From an advisory covering 34 CVEs
 before 0.0.20251023T162509-150000.1.110.1
0.0.20251023T162509-150000.1.110.1
govulncheck-vulndb
openSUSE:Tumbleweed
From an advisory covering 17 CVEs
 before 0.0.20251023T162509-1.1
0.0.20251023T162509-1.1
govulncheck-vulndb
openSUSE:Leap 16.0
From an advisory covering 1734 CVEs
 before 0.0.20260723T184607-160000.1.1
0.0.20260723T184607-160000.1.1

History

History
RecordedChangedSources
affected, facts
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2024-58267 is a high vulnerability (CVSS 8.0) in Suse Rancher, published September 26, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.24%, the 14th percentile. Fixed in github.com/rancher/rancher 2.12.2.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 1,542 references and the rest of 1 source description. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open