# CVE-2026-59826: Metabase: Arbitrary Code Execution via Database Connection Detail Bypass

> An authenticated administrator can execute arbitrary Java code on the Metabase server by registering a crafted H2 database connection due to missing validation.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-8wx2-rxp2-4x35

## What is CVE-2026-59826?

CVE-2026-59826 is a critical code injection vulnerability in metabase, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Metabase is an open-source business intelligence and embedded analytics tool. From 1.55.0 until 1.58.15.1, 1.59.12, 1.60.6.3, and 1.61.2, Metabase did not validate unsafe H2 connection properties on one database-creation code path, allowing an authenticated administrator to register a crafted H2 database connection and execute arbitrary Java code on the Metabase server. This issue is fixed in versions 1.58.15.1, 1.59.12, 1.60.6.3, and 1.61.2.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Metabase Metabase.

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

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

## Is CVE-2026-59826 being exploited?

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

## Other vulnerabilities in metabase

- [CVE-2026-72898](https://insights.sbomify.com/CVE-2026-72898/): Metabase SQL Injection (critical 10.0, exploited in the wild)
- [CVE-2021-41277](https://insights.sbomify.com/CVE-2021-41277/): Metabase GeoJSON API Local File Inclusion (critical 10.0, exploited in the wild)
- [CVE-2026-50148](https://insights.sbomify.com/CVE-2026-50148/): Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write (critical 10.0)
- [CVE-2023-37470](https://insights.sbomify.com/CVE-2023-37470/): Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint (critical 10.0)
- [CVE-2026-59827](https://insights.sbomify.com/CVE-2026-59827/): Metabase: Unsafe Deserialization of H2 Query Results (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59826 is a critical code injection vulnerability in metabase, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59826 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-59826/ (Markdown: https://insights.sbomify.com/CVE-2026-59826/index.md)
```

## Sources

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

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