Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The allocation occurs before the existing highlighting safety limits are evaluated, so memory exhaustion raises a fatal error that terminates the Elasticsearch node process. This results in a denial of service for the affected node and degrades cluster routing and health. The defect is not volumetric and does not depend on the size of the indexed data, so a single request is sufficient.
CVE-2026-72639
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-120) - 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-120/389503Vendor Advisories for CVE-2026-72639(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 23× in last 7d / 28× 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-21 09:25 UTCEG score recompute
- 2026-08-21 09:25 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 07:43 UTCEG score recompute
- 2026-08-20 07:43 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:01 UTCEG score recompute
- 2026-08-19 06:00 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 04:14 UTCEG score recompute
- 2026-08-18 04:13 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 02:29 UTCEG score recompute
- 2026-08-17 02:29 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-16 00:47 UTCEG score recompute
- 2026-08-16 00:47 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 23:04 UTCEG score recompute
- 2026-08-14 23:04 UTCGHSA enrichment
- 2026-08-13 21:22 UTCEG score recompute
- 2026-08-13 20:37 UTCEG score recompute
Show 3 moreShow fewer
- 2026-08-13 20:21 UTCEG score recompute
- 2026-08-13 19:22 UTCEG score recompute
- 2026-08-13 19:21 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-72639?
When was CVE-2026-72639 disclosed?
Is CVE-2026-72639 actively exploited?
What is the CVSS score of CVE-2026-72639?
How do I remediate CVE-2026-72639?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72639
Is Your Infrastructure Affected by CVE-2026-72639?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.