github.com/rancher/rancher

CVE-2024-58260

CVE-2024-58260 is a high-severity incorrect authorization vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.12.0, < 2.12.2. It is fixed in 2.12.2, 2.11.6, 2.10.10, 2.9.12.

Key facts
CVSS score
7.6
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/rancher/rancher
Fixed in
2.12.2, 2.11.6, 2.10.10, 2.9.12
Disclosed
2024

Summary

Impact A vulnerability has been identified within Rancher Manager where a missing server-side validation on the .username field in Rancher can allow users with update permissions on other User resources to cause denial of access for targeted accounts. Specifically: Username takeover: A user with permission to update another user’s resource can set its .username to "admin", preventing both the legitimate admin and the affected user from logging in, as Rancher enforces uniqueness at login time. Account lockout: A user with update permissions on the admin account can change the admin’s username, effectively blocking administrative access to the Rancher UI. This issue enables a malicious or compromised account with elevated update privileges on User resources to disrupt platform administration and user authentication. Note: The users with these permissions to modify accounts and resources are considered as privileged users. For more information, please consult Rancher Manger’s documentation about global permissions. Please consult the associated MITRE ATT&CK - Technique - Account Access Removal for further information about this category of attack. Patches This vulnerability is addressed by adding a new check in the webhook which blocks modifying usernames after it has been set. If it's empty then the username can be set to a username not already in use, but after that it is immutable. Patched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10 and v2.9.12. Workarounds If you can't upgrade to a fixed version, please make sure that you are only granting update permissions on users’ related resources to trusted users. References If you have any questions or comments about this advisory: Reach out to the SUSE Rancher Security team for security related inquiries. Open an issue in the Rancher repository. Verify with our support matrix and product support lifecycle.

Impact

What is incorrect authorization?

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Severity and exposure

CVE-2024-58260 has a CVSS score of 7.6 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.12.2, 2.11.6, 2.10.10, 2.9.12). Upgrading removes the vulnerable code path.

Affected versions

go

  • github.com/rancher/rancher (>= 2.12.0, < 2.12.2)
  • github.com/rancher/rancher (>= 2.11.0, < 2.11.6)
  • github.com/rancher/rancher (>= 2.10.0, < 2.10.10)
  • github.com/rancher/rancher (>= 2.9.0, < 2.9.12)

Security releases

  • github.com/rancher/rancher → 2.12.2 (go)
  • github.com/rancher/rancher → 2.11.6 (go)
  • github.com/rancher/rancher → 2.10.10 (go)
  • github.com/rancher/rancher → 2.9.12 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2024-58260 is reachable in your applications. Explore open-source security for your team.

See if CVE-2024-58260 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2024-58260 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade github.com/rancher/rancher to 2.12.2 or later
  • Upgrade github.com/rancher/rancher to 2.11.6 or later
  • Upgrade github.com/rancher/rancher to 2.10.10 or later
  • Upgrade github.com/rancher/rancher to 2.9.12 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2024-58260

What is CVE-2024-58260?

CVE-2024-58260 is a high-severity incorrect authorization vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.12.0, < 2.12.2. It is fixed in 2.12.2, 2.11.6, 2.10.10, 2.9.12. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2024-58260?

CVE-2024-58260 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/rancher/rancher are affected by CVE-2024-58260?

github.com/rancher/rancher (go) versions >= 2.12.0, < 2.12.2 is affected.

Is there a fix for CVE-2024-58260?

Yes. CVE-2024-58260 is fixed in 2.12.2, 2.11.6, 2.10.10, 2.9.12. Upgrade to this version or later.

Is CVE-2024-58260 exploitable, and should I be worried?

Whether CVE-2024-58260 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2024-58260 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-58260?
  • Upgrade github.com/rancher/rancher to 2.12.2 or later
  • Upgrade github.com/rancher/rancher to 2.11.6 or later
  • Upgrade github.com/rancher/rancher to 2.10.10 or later
  • Upgrade github.com/rancher/rancher to 2.9.12 or later

Stop the waste.
Protect your environment with Kodem.