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).

Medium CVSS 6.5

CVE id
CVE-2026-102411
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Elasticsearch
Runtimes and servers
>= 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

How to fix it

Upgrade Elasticsearch to the fixed release of the line you run: 8.19.23, 9.4.7, 9.5.3.

curl -s localhost:9200
  • Upgrade Elasticsearch (the elasticsearch image tag or packages) to the patched release with a rolling restart; on Elastic Cloud, upgrade the deployment.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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 manageindextemplates 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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.