Metabase up to 1.60.3 Snowflake JDBC driver permission

Summaryinfo

A vulnerability was found in Metabase up to 1.60.3. It has been classified as problematic. This affects an unknown part of the component Snowflake JDBC driver. Performing a manipulation results in permission. This vulnerability was named CVE-2026-50148. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Metabase up to 1.60.3. It has been classified as problematic. This affects an unknown code block of the component Snowflake JDBC driver. The manipulation with an unknown input leads to a permission vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-50148 since 06/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

Upgrading to version 1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10 or 1.60.4 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Metabase

Version

• 1.54.0
• 1.54.1
• 1.54.2
• 1.54.3
• 1.54.4
• 1.54.5
• 1.54.6
• 1.54.7
• 1.54.8
• 1.54.9
• 1.54.10
• 1.54.11
• 1.54.12
• 1.54.13
• 1.54.14
• 1.54.15
• 1.54.16
• 1.54.17
• 1.54.18
• 1.54.19
• 1.54.20
• 1.54.21
• 1.54.22
• 1.54.23
• 1.55.0
• 1.55.1
• 1.55.2
• 1.55.3
• 1.55.4
• 1.55.5
• 1.55.6
• 1.55.7
• 1.55.8
• 1.55.9
• 1.55.10
• 1.55.11
• 1.55.12
• 1.55.13
• 1.55.14
• 1.55.15
• 1.55.16
• 1.55.17
• 1.55.18
• 1.55.19
• 1.55.20
• 1.55.21
• 1.55.22
• 1.55.23
• 1.56.0
• 1.56.1
• 1.56.2
• 1.56.3
• 1.56.4
• 1.56.5
• 1.56.6
• 1.56.7
• 1.56.8
• 1.56.9
• 1.56.10
• 1.56.11
• 1.56.12
• 1.56.13
• 1.56.14
• 1.56.15
• 1.56.16
• 1.56.17
• 1.56.18
• 1.56.19
• 1.56.20
• 1.56.21
• 1.56.22
• 1.56.23
• 1.56.24
• 1.57.0
• 1.57.1
• 1.57.2
• 1.57.3
• 1.57.4
• 1.57.5
• 1.57.6
• 1.57.7
• 1.57.8
• 1.57.9
• 1.57.10
• 1.57.11
• 1.57.12
• 1.57.13
• 1.57.14
• 1.57.15
• 1.57.16
• 1.57.17
• 1.57.18
• 1.58.0
• 1.58.1
• 1.58.2
• 1.58.3
• 1.58.4
• 1.58.5
• 1.58.6
• 1.58.7
• 1.58.8
• 1.58.9
• 1.58.10
• 1.58.11
• 1.58.12
• 1.58.13
• 1.59.0
• 1.59.1
• 1.59.2
• 1.59.3
• 1.59.4
• 1.59.5
• 1.59.6
• 1.59.7
• 1.59.8
• 1.59.9
• 1.60.0
• 1.60.1
• 1.60.2
• 1.60.3

Website

• Product: https://github.com/metabase/metabase/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion