CVE-2026-82300 Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service
Attackers can cause denial of service in Elasticsearch through uncontrolled resource consumption via excessive allocation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-82300?
CVE-2026-82300 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130).
Weakness: CWE-400
Which versions are affected by CVE-2026-82300?
1 open source package ship an affected version, including elasticsearch. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
elasticsearch Bitnami | From 8.0.0 | 8.19.22, 9.4.7, 9.5.4 |
Products include Elastic Elasticsearch.
How do I fix CVE-2026-82300?
Upgrade elasticsearch to a fixed version for your release line: 8.19.22, 9.4.7 or 9.5.4.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-82300 being exploited?
There is no known exploitation of CVE-2026-82300 in the wild and no public exploit code.
Other vulnerabilities in Elastic Elasticsearch
- CVE-2015-1427 Elasticsearch Groovy Scripting Engine Remote Code Execution
- CVE-2014-3120 Elasticsearch Remote Code Execution
- CVE-2015-5377 Code injection in n/a
- CVE-2026-72649 Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution
- CVE-2026-72642 Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process
Sources
Also known as AZL-104951, BIT-elasticsearch-2026-82300, CLEANSTART-2026-JI64320, CLEANSTART-2026-SL44915, GHSA-65c4-jxc9-pv9x, MINI-2rjx-x5q8-j2w3 and 20 more.