Resource exhaustion in Elastic Elasticsearch
CVE-2026-102411
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-102411?
- CVE-2026-102411 is a medium-severity vulnerability in Elastic Elasticsearch, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 6.5/10. Published 2026-10-06.
- How severe is CVE-2026-102411?
- Medium severity. CVSS v3 base score is 6.5 out of 10.