Assessment
Why it matters
EPSS is 0.2%; technical severity is CVSS 6.5.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A user with search privileges can submit a specially crafted search request that causes a data node to exhaust available heap memory, resulting in node unavailability and cluster degradation. An attacker could leverage this vulnerability to cause cluster downtime requiring manual intervention to restore service.
Who should care
- Teams operating Elasticsearch
- Vulnerability and exposure management teams
- Security operations teams monitoring exploitation activity
Response plan
What I would do
- Confirm whether Elasticsearch is present in the environment.
- Identify affected versions and establish whether vulnerable services are exposed or reachable.
- Vendor advisory from discuss.elastic.co
- Review relevant security telemetry for evidence of attempted or successful exploitation.
- Document the remediation decision and track it to verified completion.
Treatment intelligence
Remediation intelligence
Vendor sources are listed before government and third-party guidance. Confirm product applicability and change prerequisites before deployment.
Verification noteAutomated link verification has not completed for this guidance yet.
Technical details
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CWE
- CWE-400
- Affected versions
- Elastic Elasticsearch (Start Including 8.0.0, End Excluding 8.19.15 | Start Including 9.0.0, End Excluding 9.2.9 | Start Including 9.3.0, End Excluding 9.3.4)
- Fixed versions
- Elastic Elasticsearch (Fixed from 8.19.15, 9.2.9, 9.3.4)
- Published
- 21 July 2026
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
Signal timeline
- CVE published
- Latest EPSS score: 0.2%
- Signal calculated at 11