dbcve.org
MetabaseApplication

CVE-2026-50148

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 1.54.24 / 1.55.24 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Metabase versions 1.54.0 through the listed vulnerable versions contain an RCE vulnerability where users with permission to add or edit database connections can configure a Snowflake connection to an attacker-controlled server. A flaw in the Snowflake JDBC driver allows writing arbitrary files to the Metabase host, including overwriting Metabase's own database driver files which then execute within the Metabase process.

MitigationUpgrade to fixed versions (1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10, or 1.60.4). Additionally, restrict database connection add/edit permissions to a minimal set of trusted administrators until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MetabaseApplication
Affected:>= 1.54.0, < 1.54.24>= 1.55.0, < 1.55.24>= 1.56.0, < 1.56.25>= 1.57.0, < 1.57.19>= 1.58.0, < 1.58.14>= 1.59.0, < 1.59.10>= 1.60.0, < 1.60.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Metabase version
    Check the Metabase admin panel under Settings > About, or query the application startup logs, or inspect the JAR file name if self-hosted
    Affected if Running version 1.54.0 through any version prior to 1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10, or 1.60.4
  2. Determine if Snowflake connections are configured
    Navigate to Admin > Databases in the Metabase UI and review the list of configured database connections, or inspect the Metabase application database for entries in the database table where the engine field indicates Snowflake
    Affected if Any Snowflake database connection is configured in the Metabase instance
  3. Verify database connection permissions
    Review Admin > Permissions > Data to identify which users or groups have Database connection: Create or Database connection: Edit permissions for any database or globally
    Affected if Any non-administrator user or group possesses permission to add or edit database connections
  4. Inspect JDBC driver file integrity
    Locate the Snowflake JDBC driver file in the Metabase plugins or drivers directory (typically <metabase-install-dir>/plugins or ./plugins) and compare its file hash or modification timestamp against the expected vendor release
    Affected if The Snowflake JDBC driver file has been modified, replaced, or contains unexpected contents relative to the official driver version
  5. Review audit and server logs
    Search Metabase audit logs (if enabled) and server logs for events related to Snowflake connection creation or modification, particularly connections using external or non-standard Snowflake endpoints
    Affected if Recent Snowflake connection creation or modification events exist that reference external or unexpected endpoints

A user is affected if running a Metabase version between 1.54.0 and the fixed releases AND having Snowflake database connections enabled with users permitted to add or edit those connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.54.24 / 1.55.24 / 1.56.25 or later
Fixed in 1.54.241.55.241.56.25
Interim mitigation

Upgrade to fixed versions (1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10, or 1.60.4). Additionally, restrict database connection add/edit permissions to a minimal set of trusted administrators until patching is complete.

Recommended fix High confidence

1.60.4 (or appropriate version branch: 1.54.24, 1.55.24, 1.56.25, 1.57.19, 1.58.14, 1.59.10)

  1. 1. Identify the currently running Metabase version by checking the Metabase admin panel or the deployed application
  2. 2. If running version 1.54.0 through 1.54.23: upgrade to version 1.54.24
  3. 3. If running version 1.55.0 through 1.55.23: upgrade to version 1.55.24
  4. 4. If running version 1.56.0 through 1.56.24: upgrade to version 1.56.25
  5. 5. If running version 1.57.0 through 1.57.18: upgrade to version 1.57.19
  6. 6. If running version 1.58.0 through 1.58.13: upgrade to version 1.58.14
  7. 7. If running version 1.59.0 through 1.59.9: upgrade to version 1.59.10
  8. 8. If running version 1.60.0 through 1.60.3: upgrade to version 1.60.4
Caveat Review release notes for your version branch to check for any breaking changes between your current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metabase Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50148 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data