ghsa-q82v-h4rq-5c86
Vulnerability from github
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.
{ "affected": [ { "package": { "ecosystem": "Go", "name": "github.com/rancher/rancher" }, "ranges": [ { "events": [ { "introduced": "2.12.0" }, { "fixed": "2.12.2" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/rancher/rancher" }, "ranges": [ { "events": [ { "introduced": "2.11.0" }, { "fixed": "2.11.6" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/rancher/rancher" }, "ranges": [ { "events": [ { "introduced": "2.10.0" }, { "fixed": "2.10.10" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "github.com/rancher/rancher" }, "ranges": [ { "events": [ { "introduced": "2.9.0" }, { "fixed": "2.9.12" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-58260" ], "database_specific": { "cwe_ids": [ "CWE-863" ], "github_reviewed": true, "github_reviewed_at": "2025-09-26T13:02:55Z", "nvd_published_at": "2025-10-02T12:15:28Z", "severity": "HIGH" }, "details": "### Impact\n\nA 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:\n\n- Username takeover: A user with permission to update another user\u2019s 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.\n- Account lockout: A user with update permissions on the admin account can change the admin\u2019s username, effectively blocking administrative access to the Rancher UI.\n\nThis issue enables a malicious or compromised account with elevated update privileges on User resources to disrupt platform administration and user authentication.\n\n**Note:** The users with these permissions to modify accounts and resources are considered as privileged users. For more information, please consult Rancher Manger\u2019s documentation about [global permissions](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/global-permissions).\n\nPlease consult the associated [MITRE ATT\u0026CK - Technique - Account Access Removal](https://attack.mitre.org/techniques/T1531/) for further information about this category of attack.\n\n### Patches\n\nThis vulnerability is addressed by adding a new check in the webhook which blocks modifying usernames after it has been set. If it\u0027s empty then the username can be set to a username not already in use, but after that it is immutable.\n\nPatched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10 and v2.9.12.\n\n### Workarounds\n\nIf you can\u0027t upgrade to a fixed version, please make sure that you are only granting update permissions on users\u2019 related resources to trusted users.\n\n### References\n\nIf you have any questions or comments about this advisory:\n\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).", "id": "GHSA-q82v-h4rq-5c86", "modified": "2025-10-02T15:12:02Z", "published": "2025-09-26T13:02:55Z", "references": [ { "type": "WEB", "url": "https://github.com/rancher/rancher/security/advisories/GHSA-q82v-h4rq-5c86" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-58260" }, { "type": "WEB", "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2024-58260" }, { "type": "PACKAGE", "url": "https://github.com/rancher/rancher" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:H", "type": "CVSS_V3" } ], "summary": "Rancher update on users can deny the service to the admin" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.