CVE-2026-72679: Elasticsearch Leading to Denial of Service · Uncontrolled Recursion
Affects elasticsearchSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.4.5 or 8.19.20 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.4.5, 8.19.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade elasticsearch to 9.4.5 or 8.19.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamielasticsearchpkg:bitnami/elasticsearchOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should upgrade affected Elasticsearch versions to fixed releases beyond 8.19.19 and 9.4.4. Since this is not a cloud service, administrators must apply the update manually to remediate the issue. Patch status is confirmed by the presence of patchAvailable=true and the specified fixed version ranges.
Description
A vulnerability in Elasticsearch allows an authenticated user with read-only access on a single index to cause a denial of service by triggering uncontrolled recursion in an intervals query pattern. The issue arises because Elasticsearch does not enforce its input length restriction on the user-supplied pattern, leading to unbounded recursion that exhausts the thread stack and terminates the node process. This affects specific versions of Elasticsearch and can disrupt service availability for the affected node.