Skip to main content
VulnerabilityPublished

CVE-2026-56145: Uncontrolled Resource Consumption

Source GCVE Database

0
Authoritative record:CVE-2026-56145· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 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 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 21 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ElasticElasticsearchAffected
  • >=9.4.0 <=9.4.3
  • >=8.0.0 <=8.19.17
  • >=9.0.0 <=9.3.6
Fixed in–
Mavenorg.elasticsearch/elasticsearchpkg:maven/org.elasticsearch/elasticsearchOther threatsAffected
  • =8.0.0
  • =9.0.0
  • =9.4.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict permissions to execute EQL sequence queries to trusted users only and monitor query usage to detect potential abuse.

Description

CVE-2026-56145 is a vulnerability in Elasticsearch where a low-privileged authenticated user can cause excessive memory consumption by sending a specially crafted EQL sequence query against an index they control. This uncontrolled resource consumption can lead to denial of service by crashing the Elasticsearch node.

References

Community reviews

Loading reviews…