Skip to main content
VulnerabilityPublished Updated

CVE-2026-72656: Elasticsearch Leading to Denial of Service · Excessive Memory Allocation

Affects elasticsearchSource GCVE Database

0
Compare
Authoritative record:CVE-2026-72656· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.17.10 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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 8.17.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 8.17.10.

Affected software

ProductAffectedFixed in
Bitnamielasticsearchpkg:bitnami/elasticsearchOther threatsAffected
  • >=8.11.0 <8.17.10
Fixed in
  • 8.17.10

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 version 8.17.10 or later to remediate the issue. Since this is not a cloud service, remediation requires applying the patch or upgrade manually. No known exploits are reported in the wild at this time.

Description

CVE-2026-72656 is a medium severity vulnerability in Elasticsearch affecting versions from 8.11.0 up to but not including 8.17.10. It involves memory allocation with an excessive size value during ES|QL query processing, which can lead to denial of service by exhausting heap memory on the node. An authenticated user submitting a specially crafted ES|QL query can trigger this condition, causing the node to become unavailable.

References

Community reviews

Loading reviews…