CVE-2025-23391: Rancher: Restricted Administrator can change Administrator's passwords
Impact A vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts. A Restricted Administrator should be not allowed to change the password of more privileged users unless it contains the Manage Users permissions. Rancher deployments where the Restricted Administrator role is not being used are not affected by this CVE.
Published Apr 1, 2025 · Updated Apr 11, 2025
Affected packages
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.8.0, < 2.8.14
- Fixed in
- 2.8.14
- Check
go list -m github.com/rancher/rancher
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.9.0, < 2.9.8
- Fixed in
- 2.9.8
- Check
go list -m github.com/rancher/rancher
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.4
- Fixed in
- 2.10.4
- 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 where a Restricted Administrator can change the password of Administrators and take over their accounts.
A Restricted Administrator should be not allowed to change the password of more privileged users unless it contains the Manage Users permissions.
Rancher deployments where the Restricted Administrator role is not being used are not affected by this CVE. Please consult the associated MITRE ATT&CK - Technique - Abuse Elevation Control Mechanism for further information about this category of attack.
Patches
The fix introduces a few changes:
- If the user has a manage-users verb, the user is allowed to edit/delete users. That way the Manage Users built in role will still be able to edit ALL users.
- If the user doesn't have manage-users, just edit or delete, then there is a check to ensure that the User being edited only has rules equal to or less than the editor.
Patched versions include releases v2.8.14, v2.9.8, v2.10.4 and v2.11.0
Workarounds
Users are recommended to upgrade, as soon as possible, to a version of Rancher Manager that contains the fix. If users can't upgrade, the following are recommended:
- Limit access to Rancher Restricted Admin only to trusted users.
- Downgrade Restricted Administrators to custom roles with limited permissions.
Credits
This issue was identified and reported by Xavier Duthil from OVHcloud.
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.
Credited to XavierDuthil.
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-44939
Rancher vulnerable to command injection through unsanitized YAML parameter
critical9.6Jul 1, 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, 2026CVE-2022-31247
Rancher has downstream cluster privilege escalation through cluster and project role template binding (CRTB/PRTB)
critical9.1Mar 3, 2026CVE-2023-32197
Rancher allows privilege escalation in Windows nodes due to Insecure Access Control Lists
critical9.1Oct 25, 2024
