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

> A low-privileged user can cause Elasticsearch nodes to crash via memory exhaustion using crafted queries, leading to cluster unavailability.

- **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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** AZL-106718, BIT-elasticsearch-2026-102404, GHSA-9h6g-vjpq-vfvx, MINI-4rcj-86c8-3hxr, MINI-5679-f95v-77hj, MINI-5q4j-5xw7-q682, MINI-5xfx-8r3r-2hg2, MINI-755h-c97m-qpfr, MINI-7c9f-wqm4-c99m, MINI-7cfh-x74x-2wjj, MINI-9rww-xq7f-qv8h, MINI-frh3-29qf-242f, MINI-gcq5-6224-4wq9, MINI-mmxc-35ff-5629, MINI-pv8f-rvh6-cmw2, MINI-qr3f-x8g9-mf3r, MINI-qw82-x3v2-77qv, MINI-r5xp-8f7m-wf8v, MINI-rw33-jc6c-6hmr, MINI-v4qf-3rhw-68gh, MINI-vxfg-88jj-vhrq, MINI-wp8x-jpvj-v76x, MINI-ww7h-vqxq-p58p, MINI-xrc7-h5fw-c2qj

## What is CVE-2026-102404?

CVE-2026-102404 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 6 Oct 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 can submit a specially crafted query that causes uncontrolled memory growth in the query processing engine, resulting in an out-of-memory condition that terminates the Elasticsearch node. The condition can be triggered repeatedly, including by queries embedded in shared resources, causing persistent cluster unavailability.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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.23, 9.4.8, 9.5.5 |

Products: Elastic Elasticsearch.

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

Upgrade elasticsearch to a fixed version for your release line: 8.19.23, 9.4.8 or 9.5.5.

## Is CVE-2026-102404 being exploited?

There is no known exploitation of CVE-2026-102404 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-102404 and fix it if it is affected.

What it is: CVE-2026-102404 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 6 Oct 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-102404 in the wild and no public exploit code.

Affected packages and fixed versions:
- elasticsearch (Bitnami): affected from 8.0.0; fixed in 8.19.23, 9.4.8, 9.5.5

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-102404/ (Markdown: https://insights.sbomify.com/CVE-2026-102404/index.md)
```

## Sources

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

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