cve.bz

CVE-2026-102411 elastic elasticsearch

6.5 mediumEPSS 0.3%

Medium (6.5) in elastic elasticsearch. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-102411 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102411?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102411?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102411 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Elasticsearchfrom 8.0.0 through 8.19.22
Elasticsearchfrom 9.0.0 through 9.4.6
Elasticsearchfrom 9.5.0 through 9.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux3rubygem-elasticsearchno fix listedAZL-106721

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate-impact denial of service vulnerability was found in Elasticsearch. An authenticated user who holds the manage_index_templates cluster privilege can register multiple index template resources whose user-supplied metadata each stay within the enforced per-resource size limit. When multiple such resources are retrieved together, Elasticsearch does not limit the total memory used to materialize their metadata values, so the combined retrieval can exhaust the node's available heap and cause the affected node to fail with an out-of-memory error, resulting in a denial of service. The flaw affects availability only, with no impact on confidentiality or integrity, and the Red Hat severity matches the upstream assessment (CVSS 3.1 score 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, Moderate). In Red Hat's scope, this flaw affects the community offerings for Elasticsearch (the Fedora and EPEL streams), which are tracked as affected, and a fix is being pursued for those streams.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream Elastic advisory states that there are no workarounds for this vulnerability and that the issue is resolved in Elasticsearch 9.4.7, 9.5.3, and 8.19.23; Elastic recommends upgrading to the most recent release available.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat Quay 3quay/quay-rhel8Not affected
Red Hat Quay 3quay/quay-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102411.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON