CVE-2026-72636: CWE-674 Uncontrolled Recursion in Elastic Elasticsearch
Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wildcard groups, evaluated against a sufficiently long name, exhausts the thread stack. Elasticsearch treats a stack overflow as an unrecoverable condition and shuts the node down, so the request terminates the affected node rather than failing gracefully.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-72636) in Elasticsearch's wildcard matching helper is due to uncontrolled recursion (CWE-674). The recursive implementation used to resolve wildcard patterns against names lacks bounds on recursion depth and total match operations. When a search request includes a wildcard pattern with many wildcard groups evaluated against a sufficiently long name, it exhausts the thread stack, causing a stack overflow. Elasticsearch treats such stack overflows as unrecoverable, resulting in the affected node shutting down and causing a denial of service. The affected versions explicitly identified are 8.0.0 and 9.0.0. No patch or remediation level has been published by the vendor as of the data provided.
Potential Impact
The impact is a denial of service (DoS) condition where an attacker can cause an Elasticsearch node to shut down by sending specially crafted search requests with complex wildcard patterns. This disrupts availability but does not affect confidentiality or integrity. There is no indication of exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider limiting or filtering wildcard search patterns that could trigger excessive recursion or stack exhaustion. Monitor vendor channels for updates.
CVE-2026-72636: CWE-674 Uncontrolled Recursion in Elastic Elasticsearch
Description
Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wildcard groups, evaluated against a sufficiently long name, exhausts the thread stack. Elasticsearch treats a stack overflow as an unrecoverable condition and shuts the node down, so the request terminates the affected node rather than failing gracefully.
CVSS v3.1
Score 6.5medium
Affected software
pkg:maven/org.elasticsearch/elasticsearchRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-72636) in Elasticsearch's wildcard matching helper is due to uncontrolled recursion (CWE-674). The recursive implementation used to resolve wildcard patterns against names lacks bounds on recursion depth and total match operations. When a search request includes a wildcard pattern with many wildcard groups evaluated against a sufficiently long name, it exhausts the thread stack, causing a stack overflow. Elasticsearch treats such stack overflows as unrecoverable, resulting in the affected node shutting down and causing a denial of service. The affected versions explicitly identified are 8.0.0 and 9.0.0. No patch or remediation level has been published by the vendor as of the data provided.
Potential Impact
The impact is a denial of service (DoS) condition where an attacker can cause an Elasticsearch node to shut down by sending specially crafted search requests with complex wildcard patterns. This disrupts availability but does not affect confidentiality or integrity. There is no indication of exploitation in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider limiting or filtering wildcard search patterns that could trigger excessive recursion or stack exhaustion. Monitor vendor channels for updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:29.887Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e1a7fbf8831d539b180ed
Added to database: 08/13/2026, 19:26:55 UTC
Last enriched: 08/13/2026, 20:12:46 UTC
Last updated: 08/13/2026, 22:41:18 UTC
Views: 3
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.
External Links
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.