CVE-2026-102404

Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service

Published Oct 6, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can submit a specially crafted query that causes uncontrolled memory growth in the query processing engine, resulting in an out-of-memory condition that terminates the Elasticsearch node. The condition can be triggered repeatedly, including by queries embedded in shared resources, causing persistent cluster unavailability.

Analysis

AI-generated

Technical impact

Uncontrolled Resource Consumption (CWE-400) in Elasticsearch allows a low‑privileged authenticated user to submit a crafted query that causes the query‑processing engine to allocate memory without bounds. The resulting memory pressure brings the node to an out‑of‑memory state, terminating the process and rendering the cluster unavailable. Repeated exploitation of the same query can lead to persistent denial of service.

Affected Systems

Affected are Elastic Elasticsearch instances that have not applied the recent security update. The vulnerability is known in the 8.x and 9.x families; any deployment that accepts arbitrary queries from low‑privileged accounts is at risk. The product is Elastic:Elasticsearch, and the fix is distributed through the official Elastic Security Advisory.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. The EPSS score is < 1%, indicating a low likelihood of exploitation; however, the lack of a KEV listing suggests no widespread public exploitation yet. The attack requires authenticated access, making it relatively constrained but still dangerous in multi‑tenant or shared tenancy environments where an attacker may have limited permissions to submit queries. Monitor for repeated anomalous query patterns and ensure user privileges are restrained.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check Elastic's official security advisories for updates regarding this vulnerability, and update Elasticsearch to the patched versions when available.
  • Restrict low‑privileged users from executing arbitrary queries by tightening role permissions and enforcing least privilege in query handling.
  • Monitor cluster memory usage and set alerts for abnormal consumption; consider disabling or throttling potentially dangerous query patterns if the patch cannot be applied immediately.

Generated by OpenCVE AI on October 8, 2026 at 14:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Elastic
Elastic elasticsearch
Vendors & Products Elastic
Elastic elasticsearch
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can submit a specially crafted query that causes uncontrolled memory growth in the query processing engine, resulting in an out-of-memory condition that terminates the Elasticsearch node. The condition can be triggered repeatedly, including by queries embedded in shared resources, causing persistent cluster unavailability.
Title Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
elastic
Published
Updated
Oct 6, 2026, 7:57 PM
Reserved
Sep 29, 2026, 2:06 AM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 13, 2026, 6:50 PM
Severity
Moderate
Public date
Oct 6, 2026, 7:31 PM