CVE-2026-59827 Metabase: Unsafe Deserialization of H2 Query Results

Critical 9.9 Published 9 Jul 2026 Updated 9 Jul 2026

Authenticated users can execute arbitrary code on Metabase servers by exploiting unsafe deserialization of H2 query results.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-59827?

CVE-2026-59827 is a critical unsafe deserialization vulnerability in metabase, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-502

Which versions are affected by CVE-2026-59827?

It affects 1 product.

Products include Metabase Metabase.

How do I fix CVE-2026-59827?

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

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2026-59827 being exploited?

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

Public exploit code: 1 Exploit-DB entry and 4 proofs of concept on GitHub.

Sources

Also known as GHSA-w95f-x9v9-wv36.