CVE-2026-72686: Elasticsearch Leading to Denial of Service · Uncontrolled Recursion
Affects elasticsearchSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium · fixed in 9.5.1 : update elasticsearch when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.5.1, 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 18 Nov 2026.
What to do
Upgrade elasticsearch to 9.5.1, 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 the fixed releases at or beyond 8.19.20, 9.4.5, and 9.5.1 to remediate this issue. No additional mitigation steps are indicated.
Description
CVE-2026-72686 is a medium severity vulnerability in Elasticsearch where a low-privileged authenticated user can cause a denial of service by submitting a crafted input that triggers uncontrolled recursion during input validation. This recursion exhausts the thread's stack, causing the node process to terminate unexpectedly. The flaw affects multiple Elasticsearch versions prior to fixed releases. A patch is available to address this issue.