Quick answers
- Is CVE-2026-103928 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103928 being exploited in the wild.
- How severe is CVE-2026-103928?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Metabase 1.55.0 to 1.58.15, 1.59.0 to 1.59.12, 1.60.0 to 1.60.8, 1.61.0 to 1.61.3.
- Is there a fix for CVE-2026-103928?
- Yes: fixed in Metabase 1.58.16, 1.59.13, 1.60.9, 1.61.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103928 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-103928?
- 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.
How to fix
- Fixed in: Metabase 1.58.16, 1.59.13, 1.60.9, 1.61.4
Technical details
Native queries and actions against H2 data sources fail to restrict access to host-facing built-in functions including FILE_READ, FILE_WRITE, CSVREAD, CSVWRITE, and LINK_SCHEMA. An authenticated user authorized to run native queries or actions can exploit this via network access to execute these functions and gain local file system access on the Metabase server. The vulnerability requires user authentication and native query permissions but is enabled by default with the sample database.
Affected products
- Metabase Metabase 1.55.0 to 1.58.15, 1.59.0 to 1.59.12, 1.60.0 to 1.60.8, 1.61.0 to 1.61.3
Timeline
- 2026-10-13: disclosed