Is CVE-2026-59827 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-59827 being exploited in the wild.

How severe is CVE-2026-59827?

Critical severity, with a CVSS score of 9.9, published 9 July 2026.

Which products and versions are affected?

Metabase >= 1.58.0, = 1.59.0, = 1.60.0, = 1.61.0, < 1.61.1.4.

Is there a fix for CVE-2026-59827?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-59827 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-59827?

Check whether you run Metabase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59827: Metabase unsafe deserialization in H2 native query results

Q: Is there a fix for CVE-2026-59827?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-59827 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-59827?

Check whether you run Metabase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59827 · Severity: critical · CVSS 9.9 · Published 2026-07-09

Metabase is a business intelligence tool used to visualize and analyze data. A security vulnerability exists where the application fails to properly validate data returned from certain database queries. An attacker with basic user permissions could exploit this to run unauthorized commands on the server, potentially leading to a full system takeover and theft of sensitive business data.

Technologies: Metabase. Vendors: Metabase.

Quick answers

Is CVE-2026-59827 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59827 being exploited in the wild.
How severe is CVE-2026-59827?: Critical severity, with a CVSS score of 9.9, published 9 July 2026.
Which products and versions are affected?: Metabase >= 1.58.0, < 1.58.15; >= 1.59.0, < 1.59.12; >= 1.60.0, < 1.60.6.3; >= 1.61.0, < 1.61.1.4.
Is there a fix for CVE-2026-59827?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-59827 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-59827?: Check whether you run Metabase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A deserialization vulnerability (CWE-502) exists in Metabase's handling of H2 database query results. When processing native queries against an H2 data source, Metabase does not validate the type of values returned in result columns. Specifically, H2 columns of type 'OTHER' can contain arbitrary serialized Java objects which Metabase's JDBC result handling deserializes without type checking or filtering. An authenticated attacker with permissions to run native H2 queries can craft a malicious query to achieve remote code execution (RCE) on the Metabase server. This affects instances with the default sample database enabled. The issue is fixed in versions 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4.

Affected products

Metabase Metabase >= 1.58.0, < 1.58.15; >= 1.59.0, < 1.59.12; >= 1.60.0, < 1.60.6.3; >= 1.61.0, < 1.61.1.4

Timeline

2026-06-30: advisory: GitHub Security Advisory GHSA-w95f-x9v9-wv36 published
2026-07-09: disclosed: CVE-2026-59827 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.