CVE-2026-33725: Metabase vulnerable to RCE and Arbitrary File Read via H2 JDBC INIT Injection in EE Serialization Import
Metabase is an open source business intelligence and embedded analytics tool. In Metabase Enterprise prior to versions 1.54.22, 1.55.22, 1.56.22, 1.57.16, 1.58.10, and 1.59.4, authenticated admins on Metabase Enterprise Edition can achieve Remote Code Execution (RCE) and Arbitrary File Read via the POST /api/ee/serialization/import endpoint. A crafted serialization archive injects an INIT property into the H2 JDBC spec, which can execute arbitrary SQL during a database sync. We confirmed this was possible on Metabase Cloud. This only affects Metabase Enterprise. Metabase OSS lacks the affected codepaths. All versions of Metabase Enterprise that have serialization, which dates back to at least version 1.47, are affected. Metabase Enterprise versions 1.54.22, 1.55.22, 1.56.22, 1.57.16, 1.58.10, and 1.59.4 patch the issue. As a workaround, disable the serialization import endpoint in their Metabase instance to prevent access to the vulnerable codepaths.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33725?
CVE-2026-33725 has a high severity rating due to its potential to allow remote code execution and arbitrary file read.
How do I fix CVE-2026-33725?
To remediate CVE-2026-33725, upgrade Metabase Enterprise to versions 1.54.22, 1.55.22, 1.56.22, 1.57.16, 1.58.10, or 1.59.4 or later.
Who is affected by CVE-2026-33725?
CVE-2026-33725 affects users of Metabase Enterprise versions prior to 1.54.22, 1.55.22, 1.56.22, 1.57.16, 1.58.10, and 1.59.4.
What types of attacks can CVE-2026-33725 enable?
CVE-2026-33725 can enable remote code execution and unauthorized access to sensitive files within the affected system.
How was CVE-2026-33725 discovered?
CVE-2026-33725 was identified through security research focusing on vulnerabilities in the H2 JDBC initialization process in Metabase.