Skip to content

Volcano's webhook server vulnerable to OOM due to unbounded HTTP request body size

Moderate severity GitHub Reviewed Published May 8, 2026 in volcano-sh/volcano • Updated Jun 8, 2026

Package

gomod volcano.sh/volcano (Go)

Affected versions

< 1.12.4
>= 1.13.0, < 1.13.3
>= 1.14.0, < 1.14.2

Patched versions

1.12.4
1.13.3
1.14.2

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.

References

@hzxuzhonghu hzxuzhonghu published to volcano-sh/volcano May 8, 2026
Published to the GitHub Advisory Database May 8, 2026
Reviewed May 8, 2026
Published by the National Vulnerability Database May 27, 2026
Last updated Jun 8, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(10th percentile)

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. Learn more on MITRE.

CVE ID

CVE-2026-44247

GHSA ID

GHSA-8wxp-xxp2-rcgx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.
⚡