Widespread BI platform with default H2 exposure; allows server file R/W and DB linking, enabling data theft or RCE—high-impact for many organizations.
CVE-2026-103928
Metabase H2 native-query flaw allows arbitrary file read/write on server
Is CVE-2026-103928 being exploited?
Not confirmed. CVE-2026-103928 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-103928?
CVE-2026-103928 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-103928?
Yes. A fix has been recorded for CVE-2026-103928. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-103928 affect?
CVE-2026-103928 affects Metabase 1.55.0 – 1.58.15, Metabase 1.59.0 – 1.59.12, Metabase 1.60.0 – 1.60.8, Metabase 1.61.0 – 1.61.3, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-103928?
Upgrade to 1.58.16/1.59.13/1.60.9/1.61.4; restrict native-query rights; remove H2 sample DB
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authorized native-query users can invoke H2 FILE_READ/FILE_WRITE/CSVREAD/CSVWRITE/LINK_SCHEMA to read/write server files, link DBs, enabling data exfiltration, privilege escalation or RCE.
Immediate action required
- affected>= 1.55.0 and < 1.58.16
- affected>= 1.59.0 and < 1.59.13
- affected>= 1.60.0 and < 1.60.9
- affected>= 1.61.0 and < 1.61.4
- affected>= 0.55.0 and < 0.58.15.3
- affected>= 0.59.0 and < 0.59.12.1
- affected>= 0.60.0 and < 0.60.8.1
- affected>= 0.61.0 and < 0.61.3.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.