CVE-2026-44247: Volcano: Webhook server vulnerable to OOM due to unbounded HTTP request body size
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.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44247?
CVE-2026-44247 has a high severity due to its potential impact on system stability and resource exhaustion.
How do I fix CVE-2026-44247?
To fix CVE-2026-44247, update to Volcano versions 1.14.2, 1.13.3, or 1.12.4.
What does CVE-2026-44247 affect?
CVE-2026-44247 affects the Volcano webhook server, particularly in versions before 1.14.2, 1.13.3, and 1.12.4.
What is the impact of CVE-2026-44247?
The impact of CVE-2026-44247 is that it allows any pod to send large requests, potentially crashing the webhook server due to out-of-memory (OOM) conditions.
Is there a workaround for CVE-2026-44247?
Currently, the recommended action is to update to the secure versions as there are no specific workarounds mentioned for CVE-2026-44247.