CVE-2024-58259 is a high-severity allocation of resources without limits or throttling vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.12.0, < 2.12.1. It is fixed in 2.12.1, 2.11.5, 2.10.9, 2.9.11, 0.0.0-20250813072957-aee95d4e2a41.
Impact 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. This could result in: Denial of Service (DoS): The server process may crash or become unresponsive when memory consumption exceeds available resources. Unauthenticated and authenticated exploitation: While the issue was initially observed in unauthenticated /v3-public/* endpoints, the absence of request body size limits also affected several authenticated APIs, broadening the potential attack surface. It's worth noting that other areas in Rancher do implement safeguards: requests proxied to Kubernetes APIs are subject to built-in size limits enforced by the Kubernetes API server itself, and Norman-based endpoints parse input with predefined size caps. However, the absence of similar protections in other Rancher APIs increased the risk of denial-of-service (DoS) scenarios in certain contexts. By sending large binary or text payloads to vulnerable endpoints, a malicious actor could disrupt Rancher’s availability, impacting both administrative and user operations across managed clusters. Please consult the associated MITRE ATT&CK - Technique - Network Denial of Service for further information about this category of attack. Patches This vulnerability is addressed by adding a default limit of 1MiB and a setting in case this value needs to be increased. Patched versions of Rancher include releases v2.12.1, v2.11.5, v2.10.9 and v2.9.12. Workarounds If you can't upgrade to a fixed version, please make sure that you are manually setting the request body size limits. For example, using nginx-ingress controller and only allowing requests via the ingress. For reference on how to configure the limit manually, please consult the Knowledge Base. 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.
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
CVE-2024-58259 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.12.1, 2.11.5, 2.10.9, 2.9.11, 0.0.0-20250813072957-aee95d4e2a41). Upgrading removes the vulnerable code path.
go
github.com/rancher/rancher (>= 2.12.0, < 2.12.1)github.com/rancher/rancher (>= 2.11.0, < 2.11.5)github.com/rancher/rancher (>= 2.10.0, < 2.10.9)github.com/rancher/rancher (>= 2.9.0, < 2.9.11)github.com/rancher/rancher (< 0.0.0-20250813072957-aee95d4e2a41)github.com/rancher/rancher → 2.12.1 (go)github.com/rancher/rancher → 2.11.5 (go)github.com/rancher/rancher → 2.10.9 (go)github.com/rancher/rancher → 2.9.11 (go)github.com/rancher/rancher → 0.0.0-20250813072957-aee95d4e2a41 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2024-58259 is reachable in your applications. Explore open-source security for your team.
See if CVE-2024-58259 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2024-58259 in your environment →Upgrade the following packages to resolve this vulnerability:
github.com/rancher/rancher to 2.12.1 or latergithub.com/rancher/rancher to 2.11.5 or latergithub.com/rancher/rancher to 2.10.9 or latergithub.com/rancher/rancher to 2.9.11 or latergithub.com/rancher/rancher to 0.0.0-20250813072957-aee95d4e2a41 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2024-58259 is a high-severity allocation of resources without limits or throttling vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.12.0, < 2.12.1. It is fixed in 2.12.1, 2.11.5, 2.10.9, 2.9.11, 0.0.0-20250813072957-aee95d4e2a41. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
CVE-2024-58259 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/rancher/rancher (go) versions >= 2.12.0, < 2.12.1 is affected.
Yes. CVE-2024-58259 is fixed in 2.12.1, 2.11.5, 2.10.9, 2.9.11, 0.0.0-20250813072957-aee95d4e2a41. Upgrade to this version or later.
Whether CVE-2024-58259 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
github.com/rancher/rancher to 2.12.1 or latergithub.com/rancher/rancher to 2.11.5 or latergithub.com/rancher/rancher to 2.10.9 or latergithub.com/rancher/rancher to 2.9.11 or latergithub.com/rancher/rancher to 0.0.0-20250813072957-aee95d4e2a41 or later