dbcve.org
VolcanoApplication · Linuxfoundation

CVE-2026-44247

HIGH · 7.4 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 1.12.4 / 1.13.3 or later.
See remediation →
79/100
Remediation priority · High
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 v1.14.2, v1.13.3, and v1.12.4, the Volcano webhook server does not enforce a size limit on incoming HTTP request bodies. Any in-cluster pod that can reach the webhook endpoint may send an arbitrarily large request body, potentially causing the webhook server to be killed by OOM. All Volcano deployments with the webhook server exposed to in-cluster traffic are affected. This vulnerability is fixed in v1.14.2, v1.13.3, and v1.12.4.

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

The Volcano webhook server lacks HTTP request body size validation, allowing any in-cluster pod that can reach the webhook endpoint to send arbitrarily large requests. This can cause the webhook server to exhaust memory and be killed by OOM, resulting in denial of service.

MitigationUpgrade Volcano to v1.14.2, v1.13.3, or v1.12.4 which enforce request body size limits. Additionally, consider implementing Kubernetes network policies to restrict access to the webhook endpoint to only authorized pods.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VolcanoApplication
Affected:< 1.12.4>= 1.13.0, < 1.13.3>= 1.14.0, < 1.14.2

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

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 Volcano installation
    Run 'kubectl get pods -A | grep volcano' or check for volcano-system namespace with 'kubectl get ns volcano-system'
    Affected if Volcano is not installed in the cluster (not affected)
  2. Get installed Volcano version
    Run 'kubectl get deployment -n volcano-system -o jsonpath="{.items[*].spec.template.spec.containers[*].image}"' or check the volcano-controller-manager deployment image tag
    Affected if The version cannot be determined or is below 1.12.4, between 1.13.0-1.13.2, or between 1.14.0-1.14.1
  3. Confirm webhook server is exposed
    Check for validatingwebhookconfigurations with 'kubectl get validatingwebhookconfigurations | grep volcano' and examine if the webhook is reachable from pods
    Affected if Volcano webhook configuration exists and is accessible to in-cluster pods (potential attack vector)
  4. Verify memory limits on webhook pods
    Run 'kubectl get pods -n volcano-system -l app=volcano-webhook -o json' and check spec.containers.resources.limits.memory
    Affected if No memory limits are set or limits are very high (webhook can consume excessive memory before OOM)

You are affected if Volcano is installed with a version that falls within <1.12.4, >=1.13.0 <1.13.3, or >=1.14.0 <1.14.2 AND the webhook is accessible to in-cluster pods without request size restrictions.

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
Upgrade available Upgrade to 1.12.4 / 1.13.3 / 1.14.2 or later
Fixed in 1.12.41.13.31.14.2
Interim mitigation

Upgrade Volcano to v1.14.2, v1.13.3, or v1.12.4 which enforce request body size limits. Additionally, consider implementing Kubernetes network policies to restrict access to the webhook endpoint to only authorized pods.

Recommended fix High confidence

v1.14.2 (or v1.13.3 for 1.13.x branches, v1.12.4 for 1.12.x branches)

  1. 1. Identify the current Volcano deployment version using: kubectl get deployment -n volcano-system volcano-admission -o jsonpath='{.spec.template.spec.containers[0].image}'
  2. 2. Determine the appropriate upgrade path based on your current version branch (1.12.x → 1.12.4, 1.13.x → 1.13.3, or 1.14.x → 1.14.2)
  3. 3. Upgrade to v1.14.2 (the latest stable fixed release) by updating the Volcano deployment manifests or Helm chart values
  4. 4. Apply the upgrade using kubectl apply -f <volcano-manifests.yaml> or helm upgrade
  5. 5. Verify the webhook server is running: kubectl get pods -n volcano-system -l app=volcano-admission
  6. 6. Confirm the new version: kubectl get deployment volcano-admission -n volcano-system -o jsonpath='{.spec.template.spec.containers[0].image}' | grep -E '(1.12.4|1.13.3|1.14.2)'

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

Fix this in Volcano Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44247 — 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-2026-44247 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