Quick answers
- Is CVE-2026-50148 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50148 being exploited in the wild.
- How severe is CVE-2026-50148?
- Critical severity, with a CVSS score of 10, published 15 July 2026.
- Which products and versions are affected?
- Metabase >= 1.54.0, < 1.54.24; >= 1.55.0, < 1.55.24; >= 1.56.0, < 1.56.25; >= 1.57.0, < 1.57.19; >= 1.58.0, < 1.58.14; >= 1.59.0, < 1.59.10; >= 1.60.0, < 1.60.4.
- Is there a fix for CVE-2026-50148?
- 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-50148 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-50148?
- 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
This vulnerability is a remote code execution (RCE) flaw stemming from an arbitrary file write (CWE-73) in the Snowflake JDBC driver used by Metabase. An attacker with permissions to add or edit database connections can point a Snowflake connection to a rogue server under their control. The malicious server exploits the JDBC driver to write arbitrary files to the Metabase host's filesystem, specifically targeting and replacing Metabase's own database driver files. When Metabase subsequently loads the modified driver, the attacker's code is executed within the context of the Metabase process. The fix involves bundling first-party drivers into the main application file to prevent disk-based replacement.
Affected products
- Metabase Metabase >= 1.54.0, < 1.54.24; >= 1.55.0, < 1.55.24; >= 1.56.0, < 1.56.25; >= 1.57.0, < 1.57.19; >= 1.58.0, < 1.58.14; >= 1.59.0, < 1.59.10; >= 1.60.0, < 1.60.4
Timeline
- 2026-05-28: advisory: Initial GitHub security advisory published
- 2026-07-15: disclosed: CVE published to NVD