Loading vulnerability…
Unsafe Deserialization RCE in Metabase H2 Native Query Handling
CVE-2026-59827 is a critical unsafe deserialization vulnerability in Metabase affecting instances configured with an H2 database connection, including deployments using the default sample database. In affected versions, Metabase deserializes arbitrary Java objects returned in native H2 query result columns of type OTHER without validating the object type or trust boundary. An authenticated user with permission to run native H2 queries can craft query results that cause Metabase to deserialize attacker-controlled serialized Java objects on the server, resulting in arbitrary code execution in the Metabase server process. Reported affected versions include 1.58.0 through before 1.58.15, 1.59.0 through before 1.59.12, 1.60.0 through before 1.60.6.3, and 1.61.0 through before 1.61.1.4.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote code execution on the Metabase server in the context of the Metabase application process. This can lead to full compromise of the application, theft or manipulation of data accessible to Metabase, exposure of stored credentials, secrets, and connected data source information, and potential follow-on activity such as persistence, lateral movement, or service disruption. The reported CVSS v3.1 vector indicates high impact to confidentiality, integrity, and availability.
If you can’t patch tonight, do this now.
Until patching is completed, restrict or disable access to native query execution for users who do not strictly require it, especially for H2-backed connections. Disable, remove, or avoid use of the default sample database or other H2 connections where operationally feasible. Limit authenticated access, review role assignments for native query capability, and monitor for suspicious native H2 query activity. These measures reduce exposure but do not replace vendor patching.
Patch, then assume compromise.
Upgrade Metabase to a fixed release. Reported patched versions are 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4 or later within the corresponding supported branches. Where possible, prioritize migration to the latest supported release and verify that all Metabase instances, including non-production and embedded deployments, are updated.
2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.