CVE-2026-50147 Metabase: Arbitrary File Read via MySQL Connection Property Injection

What is CVE-2026-50147?

CVE-2026-50147 is a high-severity path traversal vulnerability in metabase, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official description

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.

Weakness: CWE-88

Which versions are affected by CVE-2026-50147?

It affects 1 product.

Products include Metabase Metabase.

How do I fix CVE-2026-50147?

No fix has been published for CVE-2026-50147 yet. Limit exposure of the affected software until one is available.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-50147 being exploited?

There is no known exploitation of CVE-2026-50147 in the wild and no public exploit code.

Other vulnerabilities in metabase

• CVE-2026-72898 Metabase SQL Injection Exploited Critical 10.0
• CVE-2021-41277 Metabase GeoJSON API Local File Inclusion Exploited Critical 10.0
• CVE-2026-50148 Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write Critical 10.0
• CVE-2023-37470 Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint Critical 10.0
• CVE-2026-59827 Metabase: Unsafe Deserialization of H2 Query Results Critical 9.9

Sources

• CVE record
• NVD
• OSV
• How this page is made