Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). A user-supplied list of document fields accepted by the Kibana Playground for RAG feature was neither bounded in length nor de-duplicated before it was used to assemble the response for each matching document. A single crafted request could therefore make Kibana build a response far larger than the data it was derived from, and the resulting processing and memory pressure exhausts the resources of the Kibana instance.
CVE-2026-72674
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, 2026Kibana 9.3.8, 9.4.4 Security Update (ESA-2026-91) - Security Announcements - Discuss the Elastic Stack
https://discuss.elastic.co/t/kibana-9-3-8-9-4-4-security-update-esa-2026-91/389533Vendor Advisories for CVE-2026-72674(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 25× in last 7d / 25× 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 08:19 UTCEG score recompute
- 2026-08-20 08:19 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:29 UTCEG score recompute
- 2026-08-19 06:29 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 04:40 UTCEG score recompute
- 2026-08-18 04:40 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 02:51 UTCEG score recompute
- 2026-08-17 02:51 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 01:02 UTCEG score recompute
- 2026-08-16 01:02 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 23:12 UTCEG score recompute
- 2026-08-14 23:12 UTCGHSA enrichment
- 2026-08-13 21:23 UTCEG score recompute
- 2026-08-13 20:38 UTCEG score recompute
- 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-72674?
When was CVE-2026-72674 disclosed?
Is CVE-2026-72674 actively exploited?
What is the CVSS score of CVE-2026-72674?
How do I remediate CVE-2026-72674?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72674
Is Your Infrastructure Affected by CVE-2026-72674?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.