CVE-2026-59827: Metabase: Unsafe Deserialization of H2 Query Results
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-59827 is a critical Metabase flaw. If Metabase has an H2 database connection, including the default sample database, an authenticated user with native H2 query privileges could execute code on the Metabase server. This is a high-impact server compromise risk, but sources do not show active exploitation.
Executive priority
Treat as urgent for Metabase environments using H2 or the sample database. Prioritize upgrade and permission review because the impact is full server compromise from a low-privileged authenticated path. Internet-facing or broadly accessible Metabase instances should be handled first.
Technical view
Metabase before 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4 deserializes arbitrary Java objects from H2 native query result columns of type OTHER without validation. The issue is CWE-502 with CVSS 9.9, requiring network access, low privileges, no user interaction, and an H2 native query capability.
Likely exposure
Exposure is limited to Metabase deployments in affected version ranges that have an H2 database connection and authenticated users able to run native H2 queries. The advisory specifically includes the default sample database as a relevant H2 connection.
Exploitation context
The attacker must be authenticated and able to run native H2 queries. Successful exploitation can execute code on the Metabase server. The provided sources do not cite public exploitation, proof-of-concept activity, or CISA KEV listing.
Researcher notes
Key conditions are affected Metabase branch, H2 connection, and native H2 query permission. The root issue is unsafe Java deserialization of H2 OTHER result values. The available sources provide fixed versions and commit reference, but no evidence of in-the-wild exploitation.
Mitigation direction
Upgrade Metabase to 1.58.15, 1.59.12, 1.60.6.3, 1.61.1.4, or later applicable release.
Identify H2 connections, including the default sample database, and assess whether they are needed.
Review and restrict users permitted to run native H2 queries until upgraded.
Monitor the Metabase advisory and release notes for any additional vendor guidance.
Validation and detection
Confirm the running Metabase version is outside the affected ranges.
Check whether any H2 database connections exist, including the sample database.
Review Metabase permissions for users allowed to run native H2 queries.
Verify the deployed version matches a fixed release or later in the relevant branch.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-502 · source CWE mapping
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.