CVE-2026-102411

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

  • Medium 6.5

Description

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.

Key facts

Published
6 Oct 2026
Last changed
6 Oct 2026
Assigned by
elastic
EPSS
0.309% likely to be exploited in the next 30 days, higher than 24.122% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.5CVSS 3.1, Mediumfrom the CNA (elastic)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-130 Excessive Allocation (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
ElasticElasticsearch
  • Default status: unaffected
  • 8.0.0 up to and including 8.19.22 (affected)
  • 9.0.0 up to and including 9.4.6 (affected)
  • 9.5.0 up to and including 9.5.2 (affected)

Timeline

  1. 6 Oct 2026 Published

Weakness

References