# CVE-2026-56145: Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service

> A low-privileged user can crash Elasticsearch nodes by sending crafted EQL sequence queries that cause excessive memory consumption.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** BIT-elasticsearch-2026-56145, CLEANSTART-2026-VB21846, GHSA-5h86-ph4p-6p7w, MINI-22c2-q8xf-g27q, MINI-294p-f849-6pgp, MINI-55g8-wr8j-pgfv, MINI-67cg-p9jj-33r6, MINI-7r83-qjxh-pw3r, MINI-9gwx-x7x7-5qgw, MINI-9wgq-46qc-885w, MINI-c594-rj9g-hx9h, MINI-gfgj-jmwr-9fm2, MINI-gx38-f857-7fv4, MINI-hqf8-wpx5-fvxr, MINI-m867-25hp-xc4p, MINI-p64g-2795-pwmc, MINI-p6q2-m95v-wcwh, MINI-q3f8-vfhm-fq76, MINI-qjm3-frc6-h4rw, MINI-qwq2-9p28-8m87, MINI-v3m9-62hm-4gh4, MINI-vvrr-44wg-r475, MINI-wvx6-hw2g-4fwm, MINI-xh74-f29w-536f, MINI-xq34-cqmx-69v4

## What is CVE-2026-56145?

CVE-2026-56145 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 21 Jul 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). 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-56145?

1 open source package ship an affected version, including elasticsearch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elasticsearch` | Bitnami | From 8.0.0 | 8.19.18, 9.3.7, 9.4.4 |

Products: Elastic Elasticsearch.

## How do I fix CVE-2026-56145?

Upgrade elasticsearch to a fixed version for your release line: 8.19.18, 9.3.7 or 9.4.4.

## Is CVE-2026-56145 being exploited?

There is no known exploitation of CVE-2026-56145 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Elasticsearch

- [CVE-2015-1427](https://insights.sbomify.com/CVE-2015-1427/): Elasticsearch Groovy Scripting Engine Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2014-3120](https://insights.sbomify.com/CVE-2014-3120/): Elasticsearch Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2015-5377](https://insights.sbomify.com/CVE-2015-5377/): Code injection in n/a (critical 9.8)
- [CVE-2026-72649](https://insights.sbomify.com/CVE-2026-72649/): Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution (high 8.8)
- [CVE-2026-72642](https://insights.sbomify.com/CVE-2026-72642/): Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56145 and fix it if it is affected.

What it is: CVE-2026-56145 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56145 in the wild and no public exploit code.

Affected packages and fixed versions:
- elasticsearch (Bitnami): affected from 8.0.0; fixed in 8.19.18, 9.3.7, 9.4.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56145/ (Markdown: https://insights.sbomify.com/CVE-2026-56145/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56145
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56145
- OSV: https://osv.dev/vulnerability/CVE-2026-56145

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56145/
Summaries are generated and may contain mistakes; the official description above is the record.