Skip to main content
VulnerabilityPublished Updated

CVE-2024-58267: SUSE rancher · Insufficient Verification of Data Authenticity

Affects SUSE rancherSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SUSE rancherAffected
  • 2.9.0 – 2.12.0
4 affected builds
Fixed in–

AI-suggested

To mitigate CVE-2024-58267, organizations should prioritize upgrading Rancher to versions beyond 2.12.0 once patches are released by SUSE. Until patches are available, implement the following specific measures: 1) Enforce strict user training and awareness programs focused on phishing recognition, especially targeting users of the Rancher CLI tool. 2) Restrict Rancher CLI usage to trusted networks and devices with enhanced endpoint security controls. 3) Employ multi-factor authentication (MFA) for Rancher access to reduce the risk of token misuse. 4) Monitor Rancher authentication logs for unusual token usage patterns or access anomalies. 5) Limit the scope and permissions of tokens issued via SAML to minimize potential damage if compromised. 6) Consider deploying network-level protections such as web proxies or gateways that can detect and block phishing attempts targeting Rancher users. 7) Regularly audit and rotate authentication tokens and credentials associated with Rancher. These targeted mitigations go beyond generic advice by focusing on the specific attack vector and token protection.

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.

References

Community reviews

Loading reviews…