Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-102404— Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service

Quick assessment

Affected
Elastic Elasticsearch
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Elasticsearch 中存在不受控的资源消耗漏洞（CWE-400），可能导致通过过度分配（CAPEC-130）引发拒绝服务攻击。具有低权限的已认证用户可以提交特制的查询请求，导致查询处理引擎出现不受控制的内存增长，进而引发内存溢出，最终导致 Elasticsearch 节点终止运行。该漏洞可被反复触发，包括通过嵌入共享资源中的查询来触发，从而导致集群持续不可用。

CVSS 6.5 · Medium

Affected Version Matrix 3

VendorProduct Version RangeStatus
Elastic Elasticsearch 8.0.0≤ 8.19.22 affected
9.0.0≤ 9.4.7 affected
9.5.0≤ 9.5.4 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-102404

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Uncontrolled Resource Consumption in Elasticsearch Leading to Denial of Service
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
未加控制的资源消耗(资源穷尽)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Elastic Elasticsearch 8.0.0 ~ 8.19.22 -

II. Public POCs for CVE-2026-102404

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-102404

请登录查看更多情报信息。

Other References for CVE-2026-102404 (1)

Same Patch Batch · Elastic · 2026-10-06 · 14 CVEs total

CVE-2026-102406 8.8 HIGH Authorization Bypass Through User-Controlled Key in Kibana Leading to Cross-Tenant Data In
CVE-2026-103007 7.2 HIGH Incorrect Authorization in Elasticsearch Leading to Privilege Escalation
CVE-2026-103009 7.1 HIGH Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information D
CVE-2026-102412 6.5 MEDIUM Incorrect Authorization in Kibana Leading to Sensitive Information Disclosure
CVE-2026-102409 6.5 MEDIUM Uncontrolled Recursion in Elasticsearch Leading to Denial of Service
CVE-2026-102411 6.5 MEDIUM Allocation of Resources Without Limits or Throttling in Elasticsearch Leading to Denial of
CVE-2026-103008 6.5 MEDIUM Uncontrolled Recursion in Elasticsearch Leading to Denial of Service
CVE-2026-103005 6.5 MEDIUM Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service
CVE-2026-103006 6.5 MEDIUM Uncontrolled Recursion in Elasticsearch Leading to Denial of Service
CVE-2026-102413 6.2 MEDIUM Uncaught Exception in Elastic Endpoint Leading to Denial of Service
CVE-2026-102407 5.4 MEDIUM Incorrect Authorization in Elasticsearch Leading to Unauthorized Data Stream Modification
CVE-2026-102410 4.3 MEDIUM Missing Authorization in Kibana Leading to Information Disclosure
CVE-2026-102408 4.3 MEDIUM Inefficient Regular Expression Complexity in Elasticsearch Leading to Denial of Service

IV. Related Vulnerabilities

Same product: Elasticsearch
Same vendor: Elastic
Same weakness: CWE-400

V. Comments for CVE-2026-102404

No comments yet

Leave a comment