CVE-2026-59827

Metabase: Unsafe Deserialization of H2 Query Results

HIGH

8.8

CVSS Score

Published: July 9, 2026 at 05:43 PM UTC

Updated: July 13, 2026 at 02:41 PM UTC

1 product affected across 1 vendorMetabase

Using metabase by metabase?

Get instant alerts when new vulnerabilities affect metabase - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.8

Exploit prediction

EPSS 4%

SSVC

No known exploit

Description

Metabase is an open-source business intelligence and embedded analytics tool. Prior to 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4, Metabase instances with an H2 database connection, including the default sample database, deserialize arbitrary Java objects returned in H2 native query result columns of type OTHER without validation, allowing an authenticated user who can run native H2 queries to execute code on the Metabase server. This issue is fixed in versions 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Metabase · Metabasecontainer

95%

v < 1.58.15v < 1.59.12v < 1.60.6.3v < 1.61.1.40.58.0 ≤ v < 0.58.150.59.0 ≤ v < 0.59.120.60.0 ≤ v < 0.60.6.30.61.0 ≤ v < 0.61.1.41.58.0 ≤ v < 1.58.151.59.0 ≤ v < 1.59.121.60.0 ≤ v < 1.60.6.31.61.0 ≤ v < 1.61.1.4

Affected range stops below 0.58.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 0.59.12, so it looks safe — our inference, not a vendor statement

Affected range stops below 0.60.6.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 0.61.1.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.58.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.59.12, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.60.6.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.61.1.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (6)

x_refsource_CONFIRMVendor Advisory

Source: cverecord

https://github.com/metabase/metabase/security/advisories/GHSA-w95f-x9v9-wv36

x_refsource_MISCPatch

Source: cverecord

https://github.com/metabase/metabase/commit/00f42511fe3bc4385652a2e96862ee6fd7d42cf8

x_refsource_MISCRelease Notes

Source: cverecord

https://github.com/metabase/metabase/releases/tag/v0.58.15

x_refsource_MISCRelease Notes

Source: cverecord

https://github.com/metabase/metabase/releases/tag/v0.59.12

x_refsource_MISCRelease Notes

Source: cverecord

https://github.com/metabase/metabase/releases/tag/v0.60.6.3

x_refsource_MISCRelease Notes

Source: cverecord

https://github.com/metabase/metabase/releases/tag/v0.61.1.4

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGH[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card