On 13 October 2026, NVD published CVE-2026-103928 for Metabase, the open source BI tool. It scores 9.3 on CVSS 4.0. A user who is allowed to run native queries or actions against an H2 data source can call H2's built in file functions and read or write files on the Metabase server.
The detail that decides who is exposed is in the description: the default sample database uses H2, so the surface exists by default.
What's affected
NVD lists the affected range as 1.55.0 until 1.58.16, 1.59.13, 1.60.9 and 1.61.4, and says it is fixed in 1.58.16, 1.59.13, 1.60.9 and 1.61.4. The references point to open source release tags v0.58.15.3, v0.59.12.1 and v0.60.8.1.
The functions named are FILE_READ, FILE_WRITE, CSVREAD, CSVWRITE and LINK_SCHEMA. The attacker needs permission to run native queries or actions on the H2 database, so this is not an unauthenticated bug by itself. File access on the Metabase host can expose configuration, credentials and anything else the process can read.
To see your exposure, open Admin, Databases and look for the Sample Database or any database of type H2. Then check in Permissions which groups may write native queries on it. A broad group such as All Users with native query access to H2 is the exposed case.
What to do now
- Upgrade to 1.58.16, 1.59.13, 1.60.9 or 1.61.4 or later on your line.
- If you cannot upgrade today, remove the Sample Database and withdraw native query permission from groups that do not need it.
- Search query history for FILE_READ, FILE_WRITE, CSVREAD, CSVWRITE and LINK_SCHEMA. If you find them, rotate secrets stored in files the Metabase process can read.
Quick check
You deleted the Sample Database but still have another H2 data source. Are you safe?
No. The flaw covers any H2 data source where a user can run native queries or actions. Upgrade, and restrict native query permission.
