CVE-2026-103928: Flaw in metabase Scores 9.3 on CVSS
A newly published critical vulnerability in metabase carries a CVSS score of 9.3. Here is what is affected and how to respond.
Key points
- CVE-2026-103928 affects metabase.
- CVSS 9.3 (Critical).
- No exploitation confirmed yet.
metabase is affected by CVE-2026-103928, a security flaw that the National Vulnerability Database rates 9.3 out of 10.
At a glance
- CVE
- CVE-2026-103928
- Product
- metabase
- CVSS
- 9.3 Critical
- Weakness
- CWE-73
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Metabase is an open source business intelligence and analytics platform. From 1.55.0 until 1.58.16, 1.59.13, 1.60.9, and 1.61.4, native queries and actions against an H2 data source are passed through without restricting host-facing built-in functions. A user authorized to run native queries or actions can invoke FILE_READ, FILE_WRITE, CSVREAD, CSVWRITE, or LINK_SCHEMA to read or write arbitrary files on the Metabase server or link other databases. The default sample database uses H2, so the vulnerable surface is exposed by default. This issue is fixed in versions 1.58.16, 1.59.13, 1.60.9, and 1.61.4.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Metabase | metabase | >= 1.55.0, < 1.58.16, >= 1.59.0, < 1.59.13, >= 1.60.0, < 1.60.9, >= 1.61.0, < 1.61.4 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-103928
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-103928?
CVE-2026-103928 is a CWE-73 vulnerability in metabase.
How severe is CVE-2026-103928?
It has a CVSS score of 9.3 Critical.
Is CVE-2026-103928 being exploited?
There is no public confirmation of exploitation at the time of publication.
