Skip to main content
VulnerabilityPublished Updated

CVE-2026-72639: elasticsearch · Excessive Memory Allocation

Affects elasticsearchSource GCVE Database

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

Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.5.1 or 8.19.20 when convenient.

Data as of 16 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 9.5.1, 8.19.20
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 16 Nov 2026.

What to do

Upgrade elasticsearch to 9.5.1 or 8.19.20.

Affected software

ProductAffectedFixed in
Bitnamielasticsearchpkg:bitnami/elasticsearchOther threatsAffected
  • >=8.19.0 <8.19.20
  • >=9.3.0 <9.5.1
Fixed in
  • 8.19.20
  • 9.5.1

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.5.1 or later, where this issue is fixed. Until patched, restricting access to trusted users and monitoring for unusual search highlighting requests may reduce risk, but the primary mitigation is applying the official fix.

Description

CVE-2026-72639 is a vulnerability in Elasticsearch where the system does not enforce an upper limit on a user-supplied count in the search highlighting feature. An authenticated user with read privileges on a single index can submit a crafted search request that causes the node to allocate an excessively large internal data structure. This allocation happens before safety limits are checked, leading to memory exhaustion and a fatal error that terminates the Elasticsearch node process. This results in a denial of service affecting the node and cluster health. The vulnerability is exploitable with a single request and does not depend on the size of indexed data. A patch is available to address this issue.

References

Community reviews

Loading reviews…