CVE-2026-72678: Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72678?
The severity of CVE-2026-72678 is rated as medium with a score of 6.5.
What is CVE-2026-72678 about?
CVE-2026-72678 involves a memory allocation vulnerability in Elasticsearch that can lead to a denial of service.
How do I fix CVE-2026-72678?
To fix CVE-2026-72678, you should update to the latest version of Elasticsearch where this vulnerability has been addressed.
Who is affected by CVE-2026-72678?
CVE-2026-72678 affects authenticated users with read privileges in Elasticsearch.
What are the potential impacts of CVE-2026-72678?
The potential impact of CVE-2026-72678 is a denial of service caused by excessive memory allocation.