Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized information disclosure and case attachment integrity compromise via Privilege Abuse (CAPEC-122). An inconsistency in Kibana's file access authorization logic allows a low-privileged authenticated user to retrieve, modify, and delete case attachments that belong to feature areas they are not authorized to access. Because the access control check and the resource retrieval use different resolution mechanisms, an authenticated attacker with limited file management permissions can obtain the contents of, modify, or delete protected case attachments — such as those associated with Security Solution cases — without holding the privileges required to access those features.
CVE-2026-56147
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 17.5%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (1)
Auto-updated Jul 21, 2026Kibana 8.19.18, 9.3.7, 9.4.3 Security Update (ESA-2026-59) - Security Announcements - Discuss the Elastic Stack
https://discuss.elastic.co/t/kibana-8-19-18-9-3-7-9-4-3-security-update-esa-2026-59/388558Vendor Advisories for CVE-2026-56147(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 9× in last 7d / 9× 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-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 22:58 UTCEG score recompute
- 2026-07-22 22:58 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 21:24 UTCEG score recompute
- 2026-07-21 20:45 UTCEG score recompute
- 2026-07-21 20:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-56147?
When was CVE-2026-56147 disclosed?
Is CVE-2026-56147 actively exploited?
What is the CVSS score of CVE-2026-56147?
How do I remediate CVE-2026-56147?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56147
Is Your Infrastructure Affected by CVE-2026-56147?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.