CVE-2025-32382

Snowflake credentials logged by the Metabase backend

LOW

1.8

CVSS Score

Published: April 10, 2025 at 02:40 PM UTC

Updated: June 17, 2026 at 09:11 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

LOW1.8

Exploit prediction

EPSS 0.4%

SSVC

No known exploit

Description

Metabase is an open source Business Intelligence and Embedded Analytics tool. When admins change Snowflake connection details in Metabase (either updating a password or changing password to private key or vice versa), Metabase would not always purge older Snowflake connection details from the application database. In order to remove older and stale connection details, Metabase would try one connection method at a time and purge all the other connection methods from the application database. When Metabase found a connection that worked, it would log (log/infof "Successfully connected, migrating to: %s" (pr-str test-details)) which would then print the username and password to the logger. This is fixed in 52.17.1, 53.9.5 and 54.1.5 in both the OSS and enterprise editions. Versions 51 and lower are not impacted.

Affected

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

Metabase · Metabasecontainer

60%

v < 0.52.17.1v < 0.53.9.5v < 0.54.1.5v < 1.52.17.1v < 1.53.9.5v < 1.54.1.5

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

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

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

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

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

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

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

x_refsource_CONFIRM

Source: [email protected]

https://github.com/metabase/metabase/security/advisories/GHSA-832j-56xw-5p7f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

1.8LOWGitHub_M

Vector?

Quick Info

StatusDEFERRED

CWE

CWE-532

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