dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-32777

HIGH · 8.2 CVSS v4.0 Published 2025-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Volcano is a Kubernetes-native batch scheduling system. Prior to versions 1.11.2, 1.10.2, 1.9.1, 1.11.0-network-topology-preview.3, and 1.12.0-alpha.2, attacker compromise of either the Elastic service or the extender plugin can 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. This issue has been patched in versions 1.11.2, 1.10.2, 1.9.1, 1.11.0-network-topology-preview.3, and 1.12.0-alpha.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Volcano scheduler has a denial of service vulnerability in its Elastic service and extender plugin components. An attacker who compromises either service can cause the scheduler to crash via unrecoverable OOM panic or freeze while consuming excessive memory, effectively crossing the Kubernetes node isolation security boundary.

MitigationUpgrade Volcano to version 1.11.2, 1.10.2, 1.9.1, 1.11.0-network-topology-preview.3, or 1.12.0-alpha.2 or later. Review network policies and pod isolation to limit exposure of Elastic services and extender plugins.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Volcano is installed
    Run 'kubectl get namespaces' to list namespaces and check for 'volcano-system', or run 'helm list --all' to list Helm releases, or check for Volcano deployments via 'kubectl get deployments -A | grep -i volcano'
    Affected if No Volcano deployment found means not affected by this CVE
  2. Check Volcano scheduler version
    Run 'kubectl get deployment -n volcano-system volcano-scheduler -o jsonpath={.spec.template.spec.containers[0].image}' to get the scheduler image, or check 'helm list -n volcano-system' for the release version
    Affected if Version is before 1.11.2, 1.10.2, 1.9.1, or 1.12.0-alpha.2 (or any version below the fixed releases) - compare your version against these fixed versions to determine if vulnerable
  3. Check if Elastic service is deployed
    Run 'kubectl get pods -n volcano-system -l app=volcano-elastic' or 'kubectl get svc -n volcano-system | grep elastic' to see if the Elastic service component exists in the cluster
    Affected if Elastic service pod or service exists in the volcano-system namespace and Volcano version is below fixed releases - this component is required for the OOM vulnerability to be exploitable
  4. Check if scheduler extender plugin is configured
    Inspect the Volcano scheduler config: 'kubectl get configmap volcano-scheduler-config -n volcano-system -o yaml' or check scheduler deployment args for extender endpoints
    Affected if Scheduler extender plugin is enabled in configuration AND Volcano version is below fixed releases - the extender component must be running for the vulnerability to apply

User is affected if Volcano is installed with a version below 1.11.2/1.10.2/1.9.1/1.12.0-alpha.2 AND either the Elastic service or scheduler extender plugin components are deployed and running in the cluster

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Volcano to version 1.11.2, 1.10.2, 1.9.1, 1.11.0-network-topology-preview.3, or 1.12.0-alpha.2 or later. Review network policies and pod isolation to limit exposure of Elastic services and extender plugins.

Recommended fix High confidence

Upgrade to Volcano version 1.11.2, 1.10.2, 1.9.1, 1.11.0-network-topology-preview.3, or 1.12.0-alpha.2 (whichever aligns with your release line)

  1. 1. Identify the current Volcano version currently deployed in the cluster (e.g., via kubectl get deployment -n volcano-system or Helm release)
  2. 2. Determine which release line is currently in use (1.11.x, 1.10.x, 1.9.x, or pre-release version)
  3. 3. For release line 1.11.x: upgrade to version 1.11.2 or later
  4. 4. For release line 1.10.x: upgrade to version 1.10.2 or later
  5. 5. For release line 1.9.x: upgrade to version 1.9.1 or later
  6. 6. For 1.11.0-network-topology-preview.x: upgrade to 1.11.0-network-topology-preview.3 or later
  7. 7. For 1.12.0-alpha.x: upgrade to 1.12.0-alpha.2 or later
  8. 8. Verify the scheduler pods are running and the Elastic service and extender plugins are operational

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data