CVE-2024-58260
HIGHCVE-2024-58260 is a high-severity (CVSS 7.6) CWE-863 vulnerability in github.com/rancher/rancher. O3 Security confirms whether CVE-2024-58260 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
Blast Radius
github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancher🐹github.com/rancher/rancherReal-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
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.
Affected Packages
| 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 dependencyDetect
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 CVE-2024-58260 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 CVE-2024-58260 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 CVE-2024-58260. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-58260 in your dependencies?
O3 detects CVE-2024-58260 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.