CVE-2026-102404

Undergoing Analysis Undergoing Analysis - In Progress

BaseFortify

Publication date: 2026-10-06

Last updated on: 2026-10-13

Assigner: Elastic

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-06

Last Modified

2026-10-13

Generated

2026-10-19

AI Q&A

2026-10-07

EPSS Evaluated

2026-10-18

NVD

CVE-2026-102404

EUVD

EUVD-2026-93926

Affected Vendors & Products

Vendor	Product	Version / Range
elastic	elasticsearch	From 9.5.0 (inc) to 9.5.5 (exc)
elastic	elasticsearch	From 8.0.0 (inc) to 8.19.23 (exc)
elastic	elasticsearch	From 9.0.0 (inc) to 9.4.8 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-400	The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

Executive Summary

This is an uncontrolled resource consumption vulnerability in Elasticsearch where a low-privileged authenticated user can submit a specially crafted query that causes excessive memory allocation in the query processing engine. This leads to an out-of-memory condition, terminating the Elasticsearch node and potentially causing persistent cluster unavailability.

Detection Guidance

Detecting uncontrolled resource consumption in Elasticsearch requires monitoring memory usage and query performance. Check Elasticsearch logs for out-of-memory errors or node crashes. Use commands like 'curl -XGET 'http://localhost:9200/_nodes/stats/jvm?pretty' to inspect JVM heap usage. Monitor system metrics with tools like 'top' or 'htop' for high memory consumption by Elasticsearch processes.

Impact Analysis

The vulnerability can cause denial of service by crashing Elasticsearch nodes, making the system unavailable. If triggered repeatedly, it can lead to persistent unavailability of the Elasticsearch cluster, disrupting search and data retrieval operations.

Compliance Impact

This vulnerability can lead to denial of service by causing uncontrolled memory growth and out-of-memory conditions in Elasticsearch nodes. Persistent cluster unavailability may result from repeated exploitation, potentially disrupting data availability and processing. This could impact compliance with standards like GDPR (data availability) and HIPAA (system availability for protected health information).

Mitigation Strategies

Apply the latest Elasticsearch security patch immediately. Restrict low-privileged user access to query submission. Monitor memory usage for abnormal growth. Disable shared resources that allow query embedding until patched.

Hi! I’m here to help you understand CVE-2026-102404. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70