Vulnpedia
← Search CVEs

CVE-2026-102411

MEDIUM 6.5

Published 2026-10-06 · Last modified 2026-10-06

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.

NO EXPLOITATION SIGNALS

No known exploitation, public exploit, or elevated probability at this time. Track for changes.

Exploitation likelihood

0.3%chance of exploitation in 30 days · 24th percentile

○ In CISA KEV ○ Catalogued PoC

Impact if exploited

6.5CVSS 3.1 · MEDIUM

  • ConfidentialityNone
  • IntegrityNone
  • AvailabilityHigh

What an attacker needs

  • ✓Access: Reachable over the network — no local access needed
  • ⚠Privileges: Requires a low-privilege account
  • ✓User interaction: No user interaction needed
  • ✓Complexity: No special conditions — reliably repeatable

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

No public PoC is currently catalogued.

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Tracked sources are checked daily for recent CVEs, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Elastic

Products Elasticsearch

Weakness (CWE)

  • CWE-770: Allocation of Resources Without Limits or Throttling

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References and research data (JSON)

Vendor product assessments

  • rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-feature-server-rhel9?repository_url=registry.redhat.io/rhoai/odh-feature-server-rhel9

    • workaround: 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.
    • none available: Fix deferred
    Red Hat · CVE-2026-102411 · Updated 2026-10-21T16:10:32+00:00
  • quay/quay-rhel8 as a component of Red Hat Quay 3 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/quay-rhel8?repository_url=registry.redhat.io/quay/quay-rhel8

    Red Hat · CVE-2026-102411 · Updated 2026-10-21T16:10:32+00:00
  • quay/quay-rhel9 as a component of Red Hat Quay 3 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/quay-rhel9?repository_url=registry.redhat.io/quay/quay-rhel9

    Red Hat · CVE-2026-102411 · Updated 2026-10-21T16:10:32+00:00

Known Affected Software Configurations

VendorProductVersion range
ElasticElasticsearch≥ 8.0.0 and < 8.19.23
ElasticElasticsearch≥ 9.0.0 and < 9.4.7
ElasticElasticsearch≥ 9.5.0 and < 9.5.3

All CVSS metrics

  • MEDIUM 6.5 v3.1 · CNA Primary
    CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  • MEDIUM 6.5 v3.1 · NVD Secondary
    CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References

Advisories

Technical & other

Sources: NVD · CVE.org · EPSS