CVE-2026-72678
Reported by elastic · Published August 13, 2026
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.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Elastic | Elasticsearch | 8.19.0, 9.4.0, 9.5.0 |
| wolfi | ruby3.3-elasticsearch | * |
| chainguard | ruby3.2-elasticsearch | * |
| chainguard | ruby4.0-elasticsearch | * |
| chainguard | ruby3.4-elasticsearch | * |
| wolfi | ruby3.4-elasticsearch | * |
| Elastic | Elasticsearch | 9.5.0, 8.19.0, 9.4.0 |
| wolfi | ruby3.2-elasticsearch | * |
| chainguard | ruby3.3-elasticsearch | * |
| wolfi | ruby4.0-elasticsearch | * |
Timeline
- Aug 13, 2026 CVE Published
- Aug 14, 2026 Coalition ESS Score
- Aug 24, 2026 EPSS Score
- Aug 28, 2026 EPSS Score
- Sep 1, 2026 CVE Updated
- Sep 2, 2026 EPSS Score
- Sep 6, 2026 EPSS Score
- Sep 6, 2026 Security Advisory
- Sep 9, 2026 EPSS Score
- Sep 12, 2026 EPSS Score
- Sep 16, 2026 EPSS Score
- Sep 18, 2026 EPSS Score