Skip to main content
VulnerabilityPublished

CVE-2026-115715: Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service

Affects elasticsearchSource GCVE Database

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

Not known to be exploited · CVSS 6.5 Medium · fixed in 9.5.6 : update elasticsearch when convenient.

Data as of 17 Nov 2026, 16:04 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (elastic)CVSS 3.16.5
Patch
Available – fixed in 9.5.6, 9.4.9, 8.19.24
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 3 Nov 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.6, 9.4.9 or 8.19.24.

Affected software

ProductAffectedFixed in
Bitnamielasticsearchpkg:bitnami/elasticsearchOther threatsAffected
  • >=8.0.0 <8.19.24
  • >=9.0.0 <9.4.9
  • >=9.5.0 <9.5.6
Fixed in
  • 8.19.24
  • 9.4.9
  • 9.5.6

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

Description

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to denial of service via a specially crafted input value that is processed by an affected phonetic encoder of the analysis-phonetic plugin. An authenticated user with permission to write documents to or run searches against an index that uses an affected encoder can cause an Elasticsearch node to exhaust its heap memory. The node can become unresponsive or terminate.

References

Community reviews

Loading reviews…