CVE-2024-58260: Rancher update on users can deny the service to the admin
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.
Published Sep 26, 2025 · Updated Oct 23, 2025
Affected packages
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.12.0, < 2.12.2
- Fixed in
- 2.12.2
- Check
go list -m github.com/rancher/rancher
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.11.0, < 2.11.6
- Fixed in
- 2.11.6
- Check
go list -m github.com/rancher/rancher
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.10
- Fixed in
- 2.10.10
- Check
go list -m github.com/rancher/rancher
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.9.0, < 2.9.12
- Fixed in
- 2.9.12
- Check
go list -m github.com/rancher/rancher
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
.usernameto "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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-41052
Rancher has Privilege Escalation from Project Owner to Host
critical8.4Jul 1, 2026CVE-2026-41053
Rancher has over-inclusive team membership expansion in GitHub App authentication provider
high8.8Jul 1, 2026CVE-2026-44939
Rancher vulnerable to command injection through unsanitized YAML parameter
critical9.6Jul 1, 2026CVE-2026-25705
Rancher Extensions have arbitrary file access via path traversal
high8.4May 7, 2026CVE-2021-25320
Rancher cloud credentials can be used through proxy API by users without access
critical9.9Mar 3, 2026CVE-2021-36783
Rancher doesn't properly sanitize credentials in cluster template answers
critical9.9Mar 3, 2026
