CVE-2026-72639: Memory Allocation with Excessive Size Value in Elasticsearch Highlighting Leading to Denial of Service
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72639?
CVE-2026-72639 has a medium severity score of 6.5.
How does CVE-2026-72639 lead to Denial of Service?
CVE-2026-72639 allows an authenticated user to allocate excessive memory sizes through Elasticsearch highlighting, causing a Denial of Service.
Who is impacted by CVE-2026-72639?
Only authenticated users with read privileges on a single searchable index are impacted by CVE-2026-72639.
How can I mitigate CVE-2026-72639?
To mitigate CVE-2026-72639, ensure that you limit user access and implement strict limits on search highlighting options.
Is there a fix for CVE-2026-72639?
Yes, updating Elasticsearch to the latest version that addresses CVE-2026-72639 will resolve the vulnerability.