# CVE-2026-72678: Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service

> An authenticated user with read privileges can cause a denial of service by submitting a crafted request that triggers excessive memory allocation, crashing the Elasticsearch node.

- **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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** BIT-elasticsearch-2026-72678, CLEANSTART-2026-BW82923, CLEANSTART-2026-OE13430, GHSA-wv4v-8jh9-247v, MINI-62mm-9gwj-vg6x, MINI-7vmv-g887-rxjp, MINI-8jph-mxgp-vrph, MINI-g4rv-r23c-853w, MINI-mf4p-8894-w2mx, MINI-v8jf-h2h9-8v5m, MINI-w3fq-66h3-fvmx

## What is CVE-2026-72678?

CVE-2026-72678 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elasticsearch` | Bitnami | From 8.19.0 | 8.19.20, 9.4.5, 9.5.1 |

Products: Elastic Elasticsearch.

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

Upgrade elasticsearch to a fixed version for your release line: 8.19.20, 9.4.5 or 9.5.1.

## Is CVE-2026-72678 being exploited?

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

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

Affected packages and fixed versions:
- elasticsearch (Bitnami): affected from 8.19.0; fixed in 8.19.20, 9.4.5, 9.5.1

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

## Sources

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

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