PatchSiren cyber security CVE debrief
CVE-2026-72638 Elastic CVE debrief
An executive overview of CVE-2026-72638: Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via Input Data Manipulation (CAPEC-153). An authenticated user holding only low-privileged index creation permissions can submit a specially crafted, malformed custom analysis definition that is resolved recursively without a cycle or depth check, exhausting the thread stack and terminating the affected node. This CVE record was published on 2026-08-13T20:17:24.310Z and has not been modified since then. Affected product deployments should be reviewed for potential exposure.
- 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 Elasticsearch deployments should review and apply vendor remediation to prevent potential denial of service via Input Data Manipulation. Additionally, vulnerability management teams and platform operators should assess the affected scope of Elasticsearch deployments and prioritize remediation efforts based on the severity of potential impact on their environment. Security teams should also monitor for suspicious activity related to custom analysis definitions and inventory affected systems for potential exposure. IT professionals should ensure that proper change management and exception tracking procedures are in place for Elasticsearch updates and verify the effectiveness of compensating controls where applicable. This should be done in conjunction with reviewing official advisories and CVE records to validate affected scope, severity, and vendor guidance, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed. Compensating controls should be reviewed for exposed systems while remediation is scheduled and verified, and relevant monitoring, detection, and logs should be checked for exposed assets that need extra review. Exceptions, retest remediated assets, and close the item only after evidence is documented. This CVE record was published on 2026-08-13T20:17:24.310Z and has not been modified since then, so immediate action is recommended to prevent potential exploitation of this vulnerability in Elasticsearch deployments. Review compensating controls for exposed systems while remediation is scheduled and verified. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Track exceptions, retest remediated assets, and close the item only after evidence is documented. Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. This is
Technical summary
An authenticated user holding only low-privileged index creation permissions can submit a single request containing a specially crafted, malformed custom analysis definition that is resolved recursively without a cycle or depth check, exhausting the thread stack and terminating the affected node. This vulnerability affects Elasticsearch deployments, particularly those with low-privileged users able to create indexes. The vulnerability can be exploited via Input Data Manipulation, leading to a denial of service.
Defensive priority
Medium-priority defensive review recommended due to potential denial of service via Input Data Manipulation.
Recommended defensive actions
- Review and apply vendor remediation for Elasticsearch vulnerability
- Implement compensating controls to detect and prevent Input Data Manipulation
- Monitor for suspicious activity related to custom analysis definitions
- Inventory and assess affected scope of Elasticsearch deployments
- Exception tracking and retest procedures for Elasticsearch updates
Evidence notes
Evidence from official CVE Program record and NIST NVD detail page supports the existence of an Uncontrolled Recursion vulnerability in Elasticsearch, which can lead to denial of service. An authenticated user with low-privileged index creation permissions can submit a specially crafted, malformed custom analysis definition that is resolved recursively without a cycle or depth check, exhausting the thread stack and terminating the affected node.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72638 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72638
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72638 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72638
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-119/389498
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.