CVE-2026-44247: volcano · Uncontrolled Resource Consumption
Affects volcanoSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium · fixed in 1.14.2 : update volcano when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.14.2, 1.13.3, 1.12.4
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade volcano to 1.14.2, 1.13.3 or 1.12.4; volcano-sh/volcano to 1.12.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| volcano-shvolcano | Affected
| Fixed in
|
| volcano-shvolcano | Affected
| Fixed in
|
| volcano-shvolcano | Affected
| Fixed in
|
GitHubvolcano-sh/volcanopkg:github/volcano-sh/volcanoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Volcano versions 1.14.2, 1.13.3, and 1.12.4. Users should upgrade to one of these versions or later to remediate the issue. Since the vendor advisory indicates fixed versions, applying these official updates is the recommended mitigation. There is no indication that temporary fixes or workarounds are provided. Patch status is confirmed by the vendor's versioning information.
Description
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.