PatchSiren cyber security CVE debrief
CVE-2026-72636 Elastic CVE debrief
The Elasticsearch wildcard matching helper is vulnerable to uncontrolled recursion, which can lead to a denial of service via excessive allocation. This vulnerability affects Elasticsearch clusters and can be exploited through search requests containing wildcard patterns with a large number of wildcard groups, evaluated against sufficiently long names. Elasticsearch administrators, security teams, and IT professionals responsible for monitoring and securing Elasticsearch clusters should be aware of this vulnerability and take defensive actions. The CVE record was published on 2026-08-13T20:17:24.187Z and has not been modified since then.
- Vendor
- Elastic
- Product
- Elasticsearch
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-13
- Original CVE updated
- 2026-08-28
- Advisory published
- 2026-08-13
- Advisory updated
- 2026-08-28
Who should care
Elasticsearch administrators, security teams, and IT professionals responsible for monitoring and securing Elasticsearch clusters should be aware of this vulnerability and take defensive actions. Affected operators should review and apply vendor-provided security updates, monitor node performance, and implement compensating controls. Vulnerability management and security teams should assess Elasticsearch cluster configurations for potential vulnerabilities and prioritize defensive reviews based on the medium-priority defensive review recommendation.
Technical summary
The Elasticsearch wildcard matching helper is vulnerable to uncontrolled recursion, which can lead to a denial of service via excessive allocation. A search request containing a wildcard pattern with a large number of wildcard groups, evaluated against a sufficiently long name, can exhaust the thread stack. Elasticsearch treats a stack overflow as an unrecoverable condition and shuts the node down. This vulnerability affects Elasticsearch clusters and can be exploited through search requests containing wildcard patterns.
Defensive priority
Medium-priority defensive review recommended due to potential denial of service via excessive allocation.
Recommended defensive actions
- Review and apply vendor-provided security updates for Elasticsearch
- Monitor Elasticsearch node performance and shutdown logs for potential exploitation attempts
- Implement compensating controls such as rate limiting for search requests
- Inventory and assess Elasticsearch cluster configurations for potential vulnerabilities
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
Evidence notes
Evidence from official CVE Program record and NIST NVD detail page supports the existence of an uncontrolled recursion vulnerability in Elasticsearch wildcard matching helper. The CVE-2026-72636 record indicates a denial of service via excessive allocation. Further review of Elastic security updates and discussions may provide additional context.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72636 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72636
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72636 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72636
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-security-update-esa-2026-133/389499
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.