Skip to content

Rancher update on users can deny the service to the admin

High severity GitHub Reviewed Published Sep 25, 2025 in rancher/rancher • Updated Oct 2, 2025

Package

gomod github.com/rancher/rancher (Go)

Affected versions

>= 2.12.0, < 2.12.2
>= 2.11.0, < 2.11.6
>= 2.10.0, < 2.10.10
>= 2.9.0, < 2.9.12

Patched versions

2.12.2
2.11.6
2.10.10
2.9.12

Description

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:

References

@samjustus samjustus published to rancher/rancher Sep 25, 2025
Published to the GitHub Advisory Database Sep 26, 2025
Reviewed Sep 26, 2025
Published by the National Vulnerability Database Oct 2, 2025
Last updated Oct 2, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(1st percentile)

Weaknesses

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Learn more on MITRE.

CVE ID

CVE-2024-58260

GHSA ID

GHSA-q82v-h4rq-5c86

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.