CVE-2026-72636: elasticsearch · 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 17 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% 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 17 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 Elasticsearch to versions 8.19.20 or later, or 9.4.5 or later, where this issue is fixed. No additional mitigations are specified or required beyond applying the official fix.
Description
CVE-2026-72636 is a medium severity vulnerability in Elasticsearch affecting versions 8.0.0 up to but not including 8.19.20 and 9.0.0 up to but not including 9.4.5. It involves uncontrolled recursion in the wildcard matching helper, which can cause a denial of service by exhausting the thread stack and shutting down the node. This occurs when a search request contains a wildcard pattern with many wildcard groups evaluated against a long name, leading to a stack overflow that Elasticsearch treats as unrecoverable.