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.
CVE-2026-72678
Score 6.5 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 13, 2026
Advisory Details (1)
Auto-updated Aug 13, 2026Elasticsearch 8.19.20, 9.4.5, 9.5.1 Security Update (ESA-2026-80) - Security Announcements - Discuss the Elastic Stack
https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-9-5-1-security-update-esa-2026-80/389507Vendor Advisories for CVE-2026-72678(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 17:41 UTCGHSA enrichment
- 2026-08-19 18:27 UTCEG score recompute
- 2026-08-19 18:27 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 18:26 UTCEG score recompute
- 2026-08-18 18:26 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 19:10 UTCEG score recompute
- 2026-08-17 19:10 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 19:08 UTCEG score recompute
- 2026-08-16 19:08 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 19:53 UTCEG score recompute
- 2026-08-15 19:53 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 20:38 UTCEG score recompute
- 2026-08-14 20:38 UTCGHSA enrichment
- 2026-08-13 21:23 UTCEG score recompute
- 2026-08-13 20:57 UTCEG score recompute
- 2026-08-13 20:22 UTCEG score recompute
Show 2 moreShow fewer
- 2026-08-13 19:23 UTCEG score recompute
- 2026-08-13 19:21 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-72678?
When was CVE-2026-72678 disclosed?
Is CVE-2026-72678 actively exploited?
What is the CVSS score of CVE-2026-72678?
How do I remediate CVE-2026-72678?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72678
Is Your Infrastructure Affected by CVE-2026-72678?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.