CVE-2026-63136 json
Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service
published 2026-07-21 3 mo ago modified 2026-10-24 15 d ago also BIT-elasticsearch-2026-63136 , EUVD-2026-46404
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A user with search privileges can submit a specially crafted search request that causes a data node to exhaust available heap memory, resulting in node unavailability and cluster degradation. An attacker could leverage this vulnerability to cause cluster downtime requiring manual intervention to restore service.
Patch / fix
- bitnami elasticsearch 8.19.15, 9.2.9, 9.3.4
- elastic elasticsearch 8.19.15, 9.2.9, 9.3.4
- elasticsearch elasticsearch 8.19.15, 9.2.9, 9.3.4
- org.elasticsearch elasticsearch 8.19.15, 9.2.9, 9.3.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | elasticsearch | >=8.0.0, <8.19.15 >=9.0.0, <9.2.9 >=9.4.0, <9.3.4 |
8.19.15 9.2.9 9.3.4 |
Affected products
- Elastic Elasticsearch
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
Sources
- CVE List CVE-2026-63136
- NVD CVE-2026-63136
- OSV BIT-elasticsearch-2026-63136
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.