CVE-2026-56143 json
Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service
published 2mo ago modified 2mo ago also BIT-elasticsearch-2026-56143 , EUVD-2026-69558
- cvss
- 4.9
- 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 38%
- public exploits
- 0
- none known
Summary
Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted request that causes excessive memory consumption, which may render the affected node unavailable.
Patch / fix
- bitnami elasticsearch 8.19.20, 9.3.0
- elastic elasticsearch 8.19.20, 9.3.0
- elasticsearch elasticsearch 8.19.20, 9.3.0
- org.elasticsearch elasticsearch 8.19.20, 9.3.0
Is CVE-2026-56143 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
- 2mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | elasticsearch | >=8.0.0, <8.19.20 >=9.0.0, <9.3.0 |
8.19.20 9.3.0 |
Affected products
- Elastic Elasticsearch
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
discuss.elastic.co
/t/elasticsearch-8-19-20-9-3-0-security-update-esa-2026-47/390084
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-56143
web
Sources
- CVE List CVE-2026-56143
- NVD CVE-2026-56143
- OSV BIT-elasticsearch-2026-56143
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.