CVE-2026-72684

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw in Elasticsearch allows an authenticated user holding only read privileges to submit a small search request containing a crafted user-supplied input. Processing that input causes a specific internal component to allocate memory without any upper bound, and the allocation occurs outside the scope of the existing memory accounting controls that were intended to constrain it. The resulting out-of-memory condition is fatal and terminates the affected node process, causing a denial of service.

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 computed
Severity65% × 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, 2026
No patch confirmed yet.
generic

Elasticsearch 8.19.20, 9.4.5 Security Update (ESA-2026-76) - Security Announcements - Discuss the Elastic Stack

https://discuss.elastic.co/t/elasticsearch-8-19-20-9-4-5-security-update-esa-2026-76/389508

Vendor Advisories for CVE-2026-72684(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 / 26× 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.

  1. 2026-08-20 17:36 UTCGHSA enrichment
  2. 2026-08-19 18:27 UTCEG score recompute
  3. 2026-08-19 18:27 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 18:20 UTCEG score recompute
  6. 2026-08-18 18:20 UTCGHSA enrichment
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 19:11 UTCEG score recompute
  10. 2026-08-17 19:10 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 18:48 UTCEG score recompute
  13. 2026-08-16 18:48 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:15 UTCEPSS rescore
  17. 2026-08-15 19:40 UTCEG score recompute
  18. 2026-08-15 19:40 UTCGHSA enrichment
  19. 2026-08-15 01:31 UTCEPSS rescore
  20. 2026-08-14 20:31 UTCEG score recompute
  21. 2026-08-14 20:31 UTCGHSA enrichment
  22. 2026-08-13 21:23 UTCEG score recompute
  23. 2026-08-13 20:58 UTCEG score recompute
  24. 2026-08-13 20:22 UTCEG score recompute
  25. 2026-08-13 19:23 UTCEG score recompute
Show 1 more
  1. 2026-08-13 19:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72684?
CVE-2026-72684 is a medium vulnerability published on August 13, 2026. A flaw in Elasticsearch allows an authenticated user holding only read privileges to submit a small search request containing a crafted user-supplied input. Processing that input causes a specific internal component to allocate memory without any upper bound, and the allocation occurs outside the…
When was CVE-2026-72684 disclosed?
CVE-2026-72684 was first published in the National Vulnerability Database on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72684 actively exploited?
CVE-2026-72684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72684?
CVE-2026-72684 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-72684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72684, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72684

Explore →

Is Your Infrastructure Affected by CVE-2026-72684?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs