CVE-2026-72684: Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service
Affects elasticsearchSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.4.6 or 8.19.21 when convenient.
Data as of 16 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.6, 8.19.21
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.6 or 8.19.21.
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 apply the official fix provided by Elasticsearch to affected versions >=8.0.0 and <9.5.0. There is no indication that additional mitigations are required beyond applying the patch.
Description
CVE-2026-72684 is a medium severity vulnerability in Elasticsearch that allows an authenticated user with read privileges to cause a denial of service. By submitting a crafted search request, the user can trigger unbounded memory allocation in an internal component outside existing memory controls. This leads to an out-of-memory condition that terminates the affected node process, disrupting service availability. The vulnerability affects Elasticsearch versions from 8.0.0 up to but not including 9.5.0. A patch is available to address this issue.