CVE-2026-72639
Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The allocation occurs before the existing highlighting safety limits are evaluated, so memory exhaustion raises a fatal error that terminates the Elasticsearch node process. This results in a denial of service for the affected node and degrades cluster routing and health. The defect is not volumetric and does not depend on the size of the indexed data, so a single request is sufficient.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 6.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS probability
- 0.30%
- CWE
- CWE-789
- Published
- 2026-08-13
- Last modified
- 2026-08-13
Affected products
- Elastic Elasticsearch
- Elastic Elasticsearch
Weakness type
Related vulnerabilities
- CVE-2026-83530 — Uncontrolled Memory Allocation in cel-go
- CVE-2026-86776 — KeePass 2.35 through 2.61.1 Memory Exhaustion via KDBX Header Field Size
- CVE-2026-19204 — A client may send a WebSocket frame with an unknown opcode and a very large declared payload...
- CVE-2026-85201 — In Eclipse Ankaios versions 0.1.0 through 1.0.1, the agent does not limit the length declared by a...
- CVE-2026-85445 — MOOS-IvP through 24.8.1 BHV_IPF Demultiplexer Memory Exhaustion via Packet Count
- CVE-2026-85442 — MOOS core-moos through 10.4.0 MOOSDB Denial of Service via Unbounded Packet Allocation
- CVE-2026-84888 — RightNow-AI OpenFang tool_runner.rs shell_exec memory allocation
- CVE-2026-84857 — sigoden aichat API Endpoint serve.rs memory allocation