Quick answers
- Is CVE-2026-50147 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50147 being exploited in the wild.
- How severe is CVE-2026-50147?
- High severity, with a CVSS score of 7.6, published 15 July 2026.
- Which products and versions are affected?
- Metabase >= 1.57.0, < 1.57.19.1; >= 1.58.0, < 1.58.14.1; >= 1.59.0, < 1.59.10; >= 1.60.0, < 1.60.4.
- Is there a fix for CVE-2026-50147?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-50147 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-50147?
- Check whether you run Metabase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in Metabase's database connection configuration allows for arbitrary file read via JDBC connection property injection. An attacker with administrative privileges (required to configure database connections) can supply malicious JDBC parameters when setting up a MySQL or MariaDB connection. These parameters cause the underlying driver to read local files from the Metabase host and return their contents through SQL queries or connection validation error messages. This issue stems from improper neutralization of argument delimiters (CWE-88). Patches are available in versions 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4.
Affected products
- Metabase Metabase >= 1.57.0, < 1.57.19.1; >= 1.58.0, < 1.58.14.1; >= 1.59.0, < 1.59.10; >= 1.60.0, < 1.60.4
Timeline
- 2026-05-28: advisory: Original GitHub security advisory published
- 2026-07-15: disclosed: CVE-2026-50147 published to NVD