Memory Allocation with Excessive Size Value in Elasticsearch Highlighting Leading to Denial of Service (CVE-2026-72639)
Description
CVE-2026-72639 is a vulnerability in Elasticsearch where the system does not enforce an upper limit on a user-supplied count in the search highlighting feature. An authenticated user with read privileges on a single index can submit a crafted search request that causes the node to allocate an excessively large internal data structure. This allocation happens before safety limits are checked, leading to memory exhaustion and a fatal error that terminates the Elasticsearch node process. This results in a denial of service affecting the node and cluster health. The vulnerability is exploitable with a single request and does not depend on the size of indexed data. A patch is available to address this issue.
Affected software
pkg:bitnami/elasticsearchRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Elasticsearch's search highlighting feature accepts a user-supplied count parameter without enforcing an upper bound. The memory allocation derived from this count is not accounted for by any circuit breaker, allowing an authenticated user with read-only access on a single searchable index to trigger an excessively large memory reservation. This allocation occurs prior to the evaluation of existing highlighting safety limits, causing memory exhaustion that results in a fatal error terminating the Elasticsearch node process. The denial of service impacts node availability and cluster routing and health. The vulnerability affects Elasticsearch versions >=8.19.0 <8.19.20 and >=9.3.0 <9.5.1. A patch is available to fix this issue.
Potential Impact
An authenticated user with read privileges on a single searchable index can cause an Elasticsearch node to terminate due to memory exhaustion triggered by a single crafted search request. This denial of service degrades cluster routing and overall cluster health. The issue is not volumetric and does not require large indexed data, making exploitation feasible with minimal input.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Elasticsearch to versions 8.19.20 or later, or 9.5.1 or later, where this issue is fixed. Until patched, restricting access to trusted users and monitoring for unusual search highlighting requests may reduce risk, but the primary mitigation is applying the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-elasticsearch-2026-72639
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-72639"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
- State
- PUBLISHED
Threat ID: 6a85b4b2acd9273b492514c7
Added to database: 08/19/2026, 13:50:42 UTC
Last enriched: 08/19/2026, 14:12:32 UTC
Last updated: 10/04/2026, 10:04:22 UTC
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.