CVE-2026-33725

Metabase vulnerable to RCE and Arbitrary File Read via H2 JDBC INIT Injection in EE Serialization Import

HIGH

7.2

CVSS Score

Published: March 27, 2026 at 12:19 AM UTC

Updated: June 17, 2026 at 10:37 AM UTC

1 product affected across 1 vendorMetabase

Using metabase by metabase?

Get instant alerts when new vulnerabilities affect metabase - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.2

Exploit prediction

EPSS 0.8%

SSVC

No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Metabase · Metabasecontainer

95%

v < 1.54.22v < 1.55.22v < 1.56.22v < 1.57.16v < 1.58.10v < 1.59.41.55.0 ≤ v < 1.55.221.56.0 ≤ v < 1.56.221.57.0 ≤ v < 1.57.161.58.0 ≤ v < 1.58.101.59.0 ≤ v < 1.59.4

Affected range stops below 1.54.22, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.55.22, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.56.22, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.57.16, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.58.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.59.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/metabase/metabase/security/advisories/GHSA-fppj-vcm3-w229

References (1)

x_refsource_CONFIRMMitigationPatchVendor Advisory

Source: cverecord

https://github.com/metabase/metabase/security/advisories/GHSA-fppj-vcm3-w229

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.2HIGHGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: HIGH
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card