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.
References
| Link | Resource |
|---|---|
| https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-9-5-1-security-update-esa-2026-80/389507 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-08-13 20:17
Updated : 2026-09-01 15:28
NVD link : CVE-2026-72678
Mitre link : CVE-2026-72678
CVE.ORG link : CVE-2026-72678
JSON object : View
Products Affected
elastic
- elasticsearch
CWE
CWE-789
Memory Allocation with Excessive Size Value
