CVE-2025-32777

Workarounds

No

This issue allows an attacker who has compromised either the Elastic service or the extender plugin to cause denial of service of the scheduler. This is a privilege escalation, because Volcano users may run their Elastic service and extender plugins in separate pods or nodes from the scheduler. In the Kubernetes security model, node isolation is a security boundary, and as such an attacker is able to cross that boundary in Volcano's case if they have compromised either the vulnerable services or the pod/node in which they are deployed. The scheduler will become unavailable to other users and workloads in the cluster. The scheduler will either crash with an unrecoverable OOM panic or freeze while consuming excessive amounts of memory.

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.

Kodem intelligence

1. What is CVE-2025-32777? CVE-2025-32777 is a high-severity allocation of resources without limits or throttling vulnerability in volcano.sh/volcano (go), affecting versions < 1.9.1. It is fixed in 1.9.1, 1.10.2, 1.11.0-network-topology-preview.3, 1.11.2, 1.12.0-alpha.2. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. Which versions of volcano.sh/volcano are affected by CVE-2025-32777? volcano.sh/volcano (go) versions < 1.9.1 is affected.
3. Is there a fix for CVE-2025-32777? Yes. CVE-2025-32777 is fixed in 1.9.1, 1.10.2, 1.11.0-network-topology-preview.3, 1.11.2, 1.12.0-alpha.2. Upgrade to this version or later.
4. Is CVE-2025-32777 exploitable, and should I be worried? Whether CVE-2025-32777 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
5. What actually determines whether CVE-2025-32777 is exploitable, and how bad it is? 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.
6. How do I fix CVE-2025-32777?
   • Upgrade volcano.sh/volcano to 1.9.1 or later
   • Upgrade volcano.sh/volcano to 1.10.2 or later
   • Upgrade volcano.sh/volcano to 1.11.0-network-topology-preview.3 or later
   • Upgrade volcano.sh/volcano to 1.11.2 or later
   • Upgrade volcano.sh/volcano to 1.12.0-alpha.2 or later