# CVE-2024-58259: Rancher affected by unauthenticated Denial of Service > An attacker can cause a Denial of Service in Rancher Manager by sending excessively large payloads to API endpoints that lack size limits. - **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Sep 2025 - **Updated:** 2 Sep 2025 - **Also known as:** GHSA-4h45-jpvh-6p5j, GO-2025-3923 ## What is CVE-2024-58259? CVE-2024-58259 is a high-severity denial of service vulnerability in SUSE rancher, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability has been identified within Rancher Manager in which it did not enforce request body size limits on certain public (unauthenticated) and authenticated API endpoints. This allows a malicious user to exploit this by sending excessively large payloads, which are fully loaded into memory during processing, leading to Denial of Service (DoS). Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2024-58259? 11 open source packages ship an affected version, including github.com/rancher/rancher. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/rancher/rancher` | Go | All versions | 0.0.0-20250813072957-aee95d4e2a41 | | `github.com/rancher/rancher` | Go | All versions | 0.0.0-20250813072957-aee95d4e2a41 | | `github.com/rancher/rancher` | Go | All versions | 0.0.0-20250813072957-aee95d4e2a41 | | `github.com/rancher/rancher` | Go | From 2.10.0 | 2.10.9 | | `github.com/rancher/rancher` | Go | From 2.10.0 | 2.10.9 | | `github.com/rancher/rancher` | Go | From 2.11.0 | 2.11.5 | | `github.com/rancher/rancher` | Go | From 2.11.0 | 2.11.5 | | `github.com/rancher/rancher` | Go | From 2.12.0 | 2.12.1 | | `github.com/rancher/rancher` | Go | From 2.12.0 | 2.12.1 | | `github.com/rancher/rancher` | Go | From 2.9.0 | 2.9.11 | | `github.com/rancher/rancher` | Go | From 2.9.0 | 2.9.11 | ## How do I fix CVE-2024-58259? Upgrade github.com/rancher/rancher to a fixed version for your release line: 0.0.0-20250813072957-aee95d4e2a41, 2.10.9, 2.11.5 or 2.12.1. ## Is CVE-2024-58259 being exploited? There is no known exploitation of CVE-2024-58259 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-58259 and fix it if it is affected. What it is: CVE-2024-58259 is a high-severity denial of service vulnerability in SUSE rancher, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-58259 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/rancher/rancher (Go): affected all versions; fixed in 0.0.0-20250813072957-aee95d4e2a41 - github.com/rancher/rancher (Go): affected all versions; fixed in 0.0.0-20250813072957-aee95d4e2a41 - github.com/rancher/rancher (Go): affected all versions; fixed in 0.0.0-20250813072957-aee95d4e2a41 - github.com/rancher/rancher (Go): affected from 2.10.0; fixed in 2.10.9 - github.com/rancher/rancher (Go): affected from 2.10.0; fixed in 2.10.9 - github.com/rancher/rancher (Go): affected from 2.11.0; fixed in 2.11.5 - github.com/rancher/rancher (Go): affected from 2.11.0; fixed in 2.11.5 - github.com/rancher/rancher (Go): affected from 2.12.0; fixed in 2.12.1 - github.com/rancher/rancher (Go): affected from 2.12.0; fixed in 2.12.1 - github.com/rancher/rancher (Go): affected from 2.9.0; fixed in 2.9.11 - github.com/rancher/rancher (Go): affected from 2.9.0; fixed in 2.9.11 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-58259/ (Markdown: https://insights.sbomify.com/CVE-2024-58259/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58259 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58259 - OSV: https://osv.dev/vulnerability/CVE-2024-58259 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-58259/ Summaries are generated and may contain mistakes; the official description above is the record.