CVE-2026-72666

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

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

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

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

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized query execution against Elastic Agents that are assigned to a Kibana space the requesting user has no access to, via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A user who is authorized to run Osquery live queries in one space can have a query carried out on hosts belonging to another space, resulting in disclosure of information from those hosts to the Osquery results data stream.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

Kibana 9.4.5 Security Update (ESA-2026-97) - Security Announcements - Discuss the Elastic Stack

https://discuss.elastic.co/t/kibana-9-4-5-security-update-esa-2026-97/389537

Vendor Advisories for CVE-2026-72666(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 19:39 UTCGHSA enrichment
  2. 2026-08-19 19:30 UTCEG score recompute
  3. 2026-08-19 19:30 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 19:20 UTCEG score recompute
  6. 2026-08-18 19:20 UTCGHSA enrichment
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 19:10 UTCEG score recompute
  10. 2026-08-17 19:10 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 17:52 UTCEG score recompute
  13. 2026-08-16 17:52 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 17:43 UTCEG score recompute
  18. 2026-08-15 17:43 UTCGHSA enrichment
  19. 2026-08-15 01:31 UTCEPSS rescore
  20. 2026-08-14 17:34 UTCEG score recompute
  21. 2026-08-14 17:34 UTCGHSA enrichment
  22. 2026-08-14 16:44 UTCEG score recompute
  23. 2026-08-14 16:44 UTCGHSA enrichment
  24. 2026-08-13 20:21 UTCEG score recompute
  25. 2026-08-13 19:22 UTCEG score recompute
Show 1 more
  1. 2026-08-13 19:21 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72666?
CVE-2026-72666 is a medium vulnerability published on August 13, 2026. Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized query execution against Elastic Agents that are assigned to a Kibana space the requesting user has no access to, via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A user who is…
When was CVE-2026-72666 disclosed?
CVE-2026-72666 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72666 actively exploited?
CVE-2026-72666 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 79.8% of all scored CVEs.
What is the CVSS score of CVE-2026-72666?
CVE-2026-72666 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-72666?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72666, 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-72666

Explore →

Is Your Infrastructure Affected by CVE-2026-72666?

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

Start Free Scan →Browse All CVEs