How severe is GHSA-q82v-h4rq-5c86?

GHSA-q82v-h4rq-5c86 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q82v-h4rq-5c86?

GHSA-q82v-h4rq-5c86 affects the following packages: github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go), github.com/rancher/rancher (Go). Ecosystems affected: Go.

How do I fix GHSA-q82v-h4rq-5c86?

Update github.com/rancher/rancher to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q82v-h4rq-5c86 is resolved across your whole dependency graph.

How do I detect GHSA-q82v-h4rq-5c86 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q82v-h4rq-5c86 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q82v-h4rq-5c86?

O3 pinpoints whether GHSA-q82v-h4rq-5c86 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q82v-h4rq-5c86 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q82v-h4rq-5c86 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-q82v-h4rq-5c86?

GHSA-q82v-h4rq-5c86 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q82v-h4rq-5c86 published, and has it been updated?

GHSA-q82v-h4rq-5c86 was published on September 26, 2025 and was last updated on July 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-q82v-h4rq-5c86

HIGH

GHSA-q82v-h4rq-5c86 is a high-severity (CVSS 7.6) CWE-863 vulnerability in github.com/rancher/rancher. O3 Security confirms whether GHSA-q82v-h4rq-5c86 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Rancher update on users can deny the service to the admin

Also known asCVE-2024-58260GO-2025-3983

Published

Sep 26, 2025

Updated

Jul 2, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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:

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 Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rancher/rancher`	≥ 2.12.0&&< 2.12.2	2.12.2
🐹Go	`github.com/rancher/rancher`	≥ 2.11.0&&< 2.11.6	2.11.6
🐹Go	`github.com/rancher/rancher`	≥ 2.10.0&&< 2.10.10	2.10.10
🐹Go	`github.com/rancher/rancher`	≥ 2.9.0&&< 2.9.12	2.9.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/rancher/rancher to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q82v-h4rq-5c86 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q82v-h4rq-5c86 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q82v-h4rq-5c86. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 admi

O3 Security · Impact-Aware SCA

Is GHSA-q82v-h4rq-5c86 in your dependencies?

O3 detects GHSA-q82v-h4rq-5c86 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-q82v-h4rq-5c86

Blast Radius

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-q82v-h4rq-5c86 in your dependencies?