volcano-sh volcano up to 1.12.3/1.13.2/1.14.1 Webhook Endpoint resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in volcano-sh volcano up to 1.12.3/1.13.2/1.14.1 and classified as problematic. The affected element is an unknown function of the component Webhook Endpoint. Performing a manipulation results in resource consumption. This vulnerability is reported as CVE-2026-44247. The attacker must have access to the local network to execute the attack. No exploit exists. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in volcano-sh volcano up to 1.12.3/1.13.2/1.14.1. This affects an unknown part of the component Webhook Endpoint. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-44247 since 05/05/2026. The exploitability is told to be easy. The attack needs to be done within the local network. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.12.4, 1.13.3 or 1.14.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-32666). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 5.1
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: volcano 1.12.4/1.13.3/1.14.2
Timeline
05/05/2026 CVE reserved05/28/2026 Advisory disclosed
05/28/2026 VulDB entry created
05/30/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-8wxp-xxp2-rcgx
Status: Confirmed
CVE: CVE-2026-44247 (🔒)
GCVE (CVE): GCVE-0-2026-44247
GCVE (VulDB): GCVE-100-366537
EUVD: 🔒
Entry
Created: 05/28/2026 05:19Updated: 05/30/2026 07:00
Changes: 05/28/2026 05:19 (65), 05/30/2026 07:00 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.