Skip to content
Fencer Vulns
medium 6.5

CVE-2026-102411 json

Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of Service

published 2026-10-06 33 d ago modified 2026-10-14 25 d ago also BIT-elasticsearch-2026-102411 , EUVD-2026-93932

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Excessive Allocation (CAPEC-130). Elasticsearch enforces a size limit on the user-supplied metadata field for each individual template resource, but does not limit the total memory used when multiple such resources are retrieved together. A user holding the *manage_index_templates* cluster privilege can register multiple resources each within the individual limit. Retrieving them together materializes all of their metadata values in memory at once, exhausting available heap and causing the affected node to fail with an out-of-memory error, resulting in a denial of service.

Patch / fix

  • bitnami elasticsearch 8.19.23, 9.4.7, 9.5.3
  • elasticsearch elasticsearch 8.19.23, 9.4.7, 9.5.3
  • elastic elasticsearch 8.19.23, 9.4.7, 9.5.3
  • org.elasticsearch elasticsearch 8.19.23, 9.4.7, 9.5.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-102411 updated cvss 6.5

elasticsearch: Elasticsearch: Denial of Service via excessive memory allocation during index template retrieval

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-feature-server-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
33 d ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami elasticsearch
>=8.0.0, <8.19.23
>=9.0.0, <9.4.7
>=9.5.0, <9.5.3
8.19.23
9.4.7
9.5.3

Affected products

  • Elastic Elasticsearch

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.