CVE-2026-59826

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-09 18:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-07-30 14:32 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 9.1 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-09 18:16 UTC

Last modified

2026-07-30 14:32 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-94 · Code injection

Record status

Analyzed

Affected

• Metabase < 1.58.15.1
• Metabase < 1.59.12
• Metabase < 1.60.6.3
• Metabase < 1.61.2

Attack profile CVSS 3.1 · 9.1

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-59826.md and follow it. Check whether this project is affected by CVE-2026-59826. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge