CVE-2026-72678: CWE-789 Memory Allocation with Excessive Size Value in Elastic Elasticsearch
Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node.
AI Analysis
Technical Summary
Elasticsearch does not validate a size value from user input before using it to reserve memory for an internal data structure. An authenticated user with only read privileges can submit a single crafted request to an API endpoint that triggers an excessively large memory allocation attempt. This results in memory exhaustion, causing the Elasticsearch node process to terminate with a fatal error. This denial of service condition affects the node and degrades cluster health. The vulnerability is not volumetric, so only one request is needed regardless of heap size. The affected versions are exactly 8.19.0, 9.4.0, and 9.5.0. No patch or remediation level is currently provided by the vendor.
Potential Impact
An authenticated user with read privileges can cause an Elasticsearch node to crash by triggering excessive memory allocation, resulting in denial of service for that node and degradation of overall cluster health. There is no impact on confidentiality or integrity reported. The attack requires only a single request and does not depend on the node's heap size configuration.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is currently documented. Until a fix is available, restrict access to authenticated users and monitor for unusual node crashes.
CVE-2026-72678: CWE-789 Memory Allocation with Excessive Size Value in Elastic Elasticsearch
Description
Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node.
CVSS v3.1
Score 6.5medium
Affected software
pkg:maven/org.elasticsearch/elasticsearchRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Elasticsearch does not validate a size value from user input before using it to reserve memory for an internal data structure. An authenticated user with only read privileges can submit a single crafted request to an API endpoint that triggers an excessively large memory allocation attempt. This results in memory exhaustion, causing the Elasticsearch node process to terminate with a fatal error. This denial of service condition affects the node and degrades cluster health. The vulnerability is not volumetric, so only one request is needed regardless of heap size. The affected versions are exactly 8.19.0, 9.4.0, and 9.5.0. No patch or remediation level is currently provided by the vendor.
Potential Impact
An authenticated user with read privileges can cause an Elasticsearch node to crash by triggering excessive memory allocation, resulting in denial of service for that node and degradation of overall cluster health. There is no impact on confidentiality or integrity reported. The attack requires only a single request and does not depend on the node's heap size configuration.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is currently documented. Until a fix is available, restrict access to authenticated users and monitor for unusual node crashes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:58.730Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e1a85bf8831d539b18413
Added to database: 08/13/2026, 19:27:01 UTC
Last enriched: 08/13/2026, 19:43:38 UTC
Last updated: 08/14/2026, 00:39:28 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.