CVE-2026-102411: Elastic Elasticsearch · Unthrottled Resource Allocation
Affects Elastic ElasticsearchSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ElasticElasticsearch | Affected
| Fixed in– |
Mavenorg.elasticsearch/elasticsearchpkg:maven/org.elasticsearch/elasticsearchOther threats | Affected
| 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 an official fix is available, restrict the manage_index_templates cluster privilege to trusted users only to reduce risk. Monitor resource usage when managing index templates to detect potential abuse.
Description
CVE-2026-102411 is a resource allocation vulnerability in Elasticsearch where multiple template resources with user-supplied metadata can collectively exhaust heap memory, causing node failure and denial of service. The issue arises because while individual metadata fields have size limits, the total memory used when retrieving multiple such resources together is not limited. This affects Elasticsearch versions 8.0.0 through 8.19.22, 9.0.0 through 9.4.6, and 9.5.0 through 9.5.2. The vulnerability requires the attacker to have the manage_index_templates cluster privilege. The CVSS score is 6.5 (medium severity) with no confidentiality or integrity impact but high availability impact.