CVE-2026-94399

Uncontrolled Resource Consumption in Elasticsearch Leading to denial of service

Published Sep 26, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)

Analysis

AI-generated

Technical impact

The vulnerability is an uncontrolled resource consumption and allocation flaw (CWE‑400 and CWE‑770) in Elasticsearch. When exploited, a malicious or malformed query can force the cluster to allocate excessive memory, causing the node to become unresponsive and ultimately resulting in a denial‑of‑service condition. The weakness arises from insufficient validation of query payloads that trigger large data structures. Consequently, the confidentiality and integrity of the cluster remain unaffected, but the availability of the indexed services is compromised.

Affected Systems

The flaw affects Elasticsearch instances produced by Elastic. No specific version ranges are listed in the CNA data; therefore, based on the available CNA data, it is inferred that any deployed Elasticsearch server that has not applied the recent security updates may be vulnerable. Refer to the discussion thread for guidance on which releases contain the fix.

Risk and Exploitability

The CVSS v3.1 score of 6.5 indicates a medium severity vulnerability. The EPSS score is < 1%, and the issue is not listed in CISA’s KEV catalog, suggesting no known widespread exploitation yet. Based on the description, it is inferred that the likely attack vector is remote and requires network connectivity to the cluster, with the attacker able to send crafted queries to trigger memory exhaustion. If unmitigated, any adversary could cause repeated outages, impacting service availability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Elasticsearch security updates, including releases 8.19.22, 9.4.7, and 9.5.4 as referenced in Elastic’s discussion thread.
  • Configure query and allocation limits (e.g., indices.breaker.fielddata.limit, indices.breaker.request.limit, and search.max_buckets) to restrict the amount of memory each request can consume.
  • Implement rate limiting and monitor cluster health metrics; set alerts for abnormal memory usage so potential denial‑of‑service attempts can be detected early.

Generated by OpenCVE AI on September 30, 2026 at 05:13 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
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Elastic
Elastic elasticsearch
Vendors & Products Elastic
Elastic elasticsearch
Type Values Removed Values Added
Description Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
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
Sep 26, 2026, 11:00 PM
Reserved
Sep 21, 2026, 1:29 PM
Status
Analyzed
Published
Sep 26, 2026, 9:16 PM
Modified
Sep 29, 2026, 8:15 PM
Severity
Moderate
Public date
Sep 26, 2026, 8:42 PM