CVE-2026-44247 — volcano
MEDIUMCVE-2026-44247 is a medium-severity (CVSS 6.8) Uncontrolled Resource Consumption vulnerability in volcano.sh/volcano. A fix is available for volcano.sh/volcano — see the affected versions and patch details below.
Volcano: Webhook server vulnerable to OOM due to unbounded HTTP request body size
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44247.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-44247 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
volcano.sh/volcano🐹volcano.sh/volcano🐹volcano.sh/volcanoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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.
Patches
This issue will be fixed in the following versions:
- v1.14.2
- v1.13.3
- v1.12.4
Users running versions below these should upgrade accordingly.
Workarounds
No known workarounds. Upgrade to the patched versions listed above.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | volcano.sh/volcano | all versions | 1.12.4go get volcano.sh/volcano@v1.12.4 |
| 🐹Go | volcano.sh/volcano | ≥ 1.13.0&&< 1.13.3 | 1.13.3go get volcano.sh/volcano@v1.13.3 |
| 🐹Go | volcano.sh/volcano | ≥ 1.14.0&&< 1.14.2 | 1.14.2go get volcano.sh/volcano@v1.14.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for volcano.sh/volcano, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update volcano.sh/volcano to 1.12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44247 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-44247 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-44247. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-44247 in your dependencies?
O3 Security finds CVE-2026-44247 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.