What is the CVSS score of CVE-2026-50148?

CVE-2026-50148 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.4%.

Which versions of Metabase are affected by CVE-2026-50148?

A critical vulnerability in Metabase analytics platform allows database administrators with connection-management privileges to execute arbitrary code on the analytics infrastructure, risking…. A patch is available.

How to fix or mitigate CVE-2026-50148?

Within 24 hours, identify all Metabase deployments running versions 1.54.0 or later and confirm which instances have Snowflake connections configured; note that while no public exploit has been identified at time of analysis, the vulnerability carries a CVSS score of 10.0. Within 7 days, apply the vendor-released patch referenced in advisory GHSA-r6x2-rchx-q9g9 to all affected instances and restrict database-connection management rights to a minimal set of vetted administrators with audit logging enabled. Within 30 days, verify patch rollout across all Metabase deployments, audit all recent database-connection configuration changes for unauthorized activity, and implement network segmentation to isolate Metabase from systems holding sensitive data.

Metabase CVE-2026-50148

EUVD-2026-44701 CRITICAL

External Control of File Name or Path (CWE-73)

2026-07-15 GitHub_M

RCE Metabase

9.1

CVSS 3.1 · NVD

Severity by source

Vendor (GitHub_M) PRIMARY

CRITICAL

qualitative

NVD

9.1 CRITICAL

AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

vuln.today AI

9.1 CRITICAL

Requires a privileged connection-management/admin user (PR:H, not PR:N), driver file write escapes the app to compromise the whole host (S:C) yielding full host RCE (C/I/A:H).

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (GitHub_M).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVSS changed

Jul 30, 2026 - 14:37 NVD

10.0 (CRITICAL) 9.1 (CRITICAL)

Patch available

Jul 15, 2026 - 17:48 EUVD

Analysis Generated

Jul 15, 2026 - 15:49 vuln.today

CVE Published

Jul 15, 2026 - 15:18 cve.org

CRITICAL 10.0

DescriptionNVD

Metabase is an open-source business intelligence and embedded analytics tool. From 1.54.0 until 1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10, and 1.60.4, a Metabase user with permission to add or edit a database connection can achieve remote code execution on the Metabase server by configuring a Snowflake connection to an attacker-controlled server, because a flaw in the Snowflake JDBC driver can write arbitrary files anywhere on the Metabase host, including replacing one of Metabase's own database driver files that later executes inside the Metabase process. This issue is fixed in versions 1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10, and 1.60.4.

AnalysisAI

Remote code execution in Metabase (open-source business intelligence platform) versions 1.54.0 through the fixed releases lets a user holding database-connection management rights run arbitrary code on the Metabase server. By pointing a Snowflake connection at an attacker-controlled server, a flaw in the bundled Snowflake JDBC driver writes attacker files anywhere on the host, overwriting one of Metabase's own driver files that later executes inside the Metabase process. There is no public exploit identified at time of analysis, but the vendor rates it CVSS 10.0 and a vendor security advisory (GHSA-r6x2-rchx-q9g9) confirms both the flaw and fixed versions.

Technical ContextAI

Metabase embeds JDBC drivers to connect to external databases; one of these is the Snowflake JDBC driver. The root cause is CWE-73 (External Control of File Name or Path): when a Metabase database connection is configured to reach out to a Snowflake endpoint, a malicious Snowflake server can abuse the driver's handling of server-supplied data to write files to arbitrary locations on the Metabase host filesystem. Because Metabase dynamically loads its database driver files at runtime, an attacker who overwrites a legitimate driver artifact with a malicious one gains code execution inside the JVM that runs Metabase - turning a data-connectivity feature into a host-level RCE primitive. The CPE cpe:2.3:a:metabase:metabase:*:*:*:*:*:*:*:* identifies Metabase itself as the affected product, though the underlying defect lives in the Snowflake JDBC driver dependency.

RemediationAI

Vendor-released patch: upgrade to 1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10, or 1.60.4 depending on your current branch, per the advisory at https://github.com/metabase/metabase/security/advisories/GHSA-r6x2-rchx-q9g9. Until you can patch, the most effective compensating control is to restrict who can add or edit database connections - audit and minimize the set of users and groups with database-management/admin permission, since that privilege is the precondition for exploitation (trade-off: legitimate operators lose self-service ability to add data sources). Additionally, apply egress network controls so the Metabase host cannot make outbound connections to arbitrary attacker-controlled Snowflake endpoints, allowlisting only known, trusted Snowflake hosts (trade-off: breaks connections to any Snowflake instance not on the allowlist and requires maintenance as legitimate endpoints change). Avoid inventing driver-level workarounds; the JDBC driver flaw is remediated in the patched Metabase releases.