# CVE-2026-103928: Metabase: Arbitrary File Read/Write via Unsafe H2 Built-in Functions

> Authorized users can read or write arbitrary files on the Metabase server via unsafe H2 built-in functions in native queries.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-cwxq-fmxq-jv8h

## What is CVE-2026-103928?

CVE-2026-103928 is a critical path traversal vulnerability in metabase, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-103928?


## How do I fix CVE-2026-103928?

No fix has been published for CVE-2026-103928 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103928 being exploited?

There is no known exploitation of CVE-2026-103928 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103928 and fix it if it is affected.

What it is: CVE-2026-103928 is a critical path traversal vulnerability in metabase, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103928 in the wild and no public exploit code.

Affected product: metabase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103928/ (Markdown: https://insights.sbomify.com/CVE-2026-103928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103928
- OSV: https://osv.dev/vulnerability/CVE-2026-103928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103928/
Summaries are generated and may contain mistakes; the official description above is the record.