Metabase is an open-source business intelligence and embedded analytics tool. From 1.57.0 until 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4, an attacker who can configure a Metabase database connection can read arbitrary files from the Metabase server's filesystem by adding unsafe JDBC parameters to a MySQL or MariaDB connection, causing the driver to read files from the Metabase host and expose the contents through queries against the connected database or through validation error messages. This issue is fixed in versions 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4.
CVE-2026-50147
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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.6
- EG Score
- 7.6(medium)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity76% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 10.0%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (1)
Auto-updated Jul 15, 2026Arbitrary File Read via MySQL Connection Property Injection · Advisory · metabase/metabase · GitHub
https://github.com/metabase/metabase/security/advisories/GHSA-mfpj-crjq-xrcpWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 11× 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-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 15:56 UTCEG score recompute
- 2026-07-15 15:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-88
- CVE-2018-3856EG 9.9CRITICAL
- CVE-2020-28026EG 9.8EPSS 95%CRITICAL
- CVE-2020-21224EG 9.8EPSS 98%CRITICAL
- CVE-2020-25494EG 9.8EPSS 98%CRITICAL
- CVE-2020-5648EG 9.8CRITICAL
- CVE-2020-15692EG 9.8EPSS 90%CRITICAL
- CVE-2020-5599EG 9.8CRITICAL
- CVE-2020-12641EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2019-12148EG 9.8CRITICAL
- CVE-2019-12147EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-50147?
When was CVE-2026-50147 disclosed?
Is CVE-2026-50147 actively exploited?
What is the CVSS score of CVE-2026-50147?
How do I remediate CVE-2026-50147?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-50147
Is Your Infrastructure Affected by CVE-2026-50147?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.