CVE-2026-56145 json
Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service
published 3mo ago modified 18d ago also BIT-elasticsearch-2026-56145 , EUVD-2026-46395
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- 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 low-privileged authenticated user with permission to execute EQL sequence queries against an index they control can send a specially crafted query that triggers excessive memory consumption, causing the Elasticsearch node to crash.
Patch / fix
- bitnami elasticsearch 8.19.18, 9.3.7, 9.4.4
- elastic elasticsearch 8.19.18, 9.3.7, 9.4.4
- elasticsearch elasticsearch 8.19.18, 9.3.7, 9.4.4
- org.elasticsearch elasticsearch 8.19.18, 9.3.7, 9.4.4
Is CVE-2026-56145 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-11).
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.18 >=9.0.0, <9.3.7 >=9.4.0, <9.4.4 |
8.19.18 9.3.7 9.4.4 |
Affected products
- Elastic Elasticsearch
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
Sources
- CVE List CVE-2026-56145
- NVD CVE-2026-56145
- OSV BIT-elasticsearch-2026-56145
Fencer Intel 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.