CVE-2026-50147
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 · uneditedMetabase is an open-source business intelligence and embedded analytics tool. From 1.57.0 until 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4, an attacker who can configure a Metabase database connection can read arbitrary files from the Metabase server's filesystem by adding unsafe JDBC parameters to a MySQL or MariaDB connection, causing the driver to read files from the Metabase host and expose the contents through queries against the connected database or through validation error messages. This issue is fixed in versions 1.57.19.1, 1.58.14.1, 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 confidenceA path traversal/file inclusion vulnerability in Metabase allows attackers with database connection configuration privileges to read arbitrary files from the server filesystem by injecting unsafe JDBC parameters (like LOAD DATA LOCAL INFILE) into MySQL/MariaDB connection strings, causing the database driver to read and exfiltrate file contents through query results or error messages.
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>= 1.57.0, < 1.57.19.1>= 1.58.0, < 1.58.14.1>= 1.59.0, < 1.59.10>= 1.60.0, < 1.60.4CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Metabase versionCheck the running Metabase instance version via the UI (Settings > About) or by inspecting the metabase JAR file name, or by querying the /api/health endpoint which returns version informationAffected if The installed version is before 1.57.19.1, 1.58.14.1, 1.59.10, or 1.60.4 (i.e., any version below the fixed releases)
-
Verify current user has database connection permissionsLog into Metabase as the target user and navigate to Settings > Admin > Databases, or check if the user role grants 'database connection' or 'settings' management permissionsAffected if The user account in question has privileges to create or edit database connections (typically admin or a custom role with database connection config rights)
-
Locate MySQL/MariaDB database connectionsIn Metabase admin panel, go to Settings > Admin > Databases and review the configured connections. Identify any connections where the 'Engine' is set to MySQL or MariaDBAffected if At least one MySQL or MariaDB database connection is configured in Metabase
-
Inspect JDBC connection string parametersAccess the database connection settings for any MySQL/MariaDB connection. Examine the 'JDBC connection string' field or the connection URL for the presence of parameters like 'allowLoadLocalInfile', 'allowUrlInLocalInfile', or other JDBC parameters that could enable file loadingAffected if The JDBC connection string contains parameters such as 'allowLoadLocalInfile=true' or 'allowUrlInLocalInfile=true', or if arbitrary JDBC parameters can be appended to the connection string
-
Review database driver behaviorTest by attempting to use a SQL query that references a local file path (e.g., SELECT * FROM LOAD DATA LOCAL INFILE '/etc/passwd') through Metabase's native query editor on the MySQL/MariaDB connection, if you have permission to run raw queriesAffected if The query executes without being blocked and returns file contents, indicating the driver permits local file loading through the connection
A user is affected if they run a Metabase version prior to the fixed releases AND have database connection configuration privileges AND have a MySQL/MariaDB connection configured, particularly if the connection allows JDBC parameters that enable local file loading.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.57.19.11.58.14.11.59.10
Upgrade Metabase to versions 1.57.19.1, 1.58.14.1, 1.59.10, or 1.60.4. Additionally, restrict database connection configuration permissions to trusted admins only and apply least-privilege principles to the service account running Metabase.
Upgrade to 1.60.4 (latest stable) or the latest version in your current branch: 1.57.19.1, 1.58.14.1, 1.59.10, or 1.60.4
- Identify the currently running Metabase version by checking the Metabase admin UI or the deployment configuration
- Determine which version branch (1.57.x, 1.58.x, 1.59.x, or 1.60.x) your instance is running on
- If running version 1.57.x, upgrade to version 1.57.19.1 or later
- If running version 1.58.x, upgrade to version 1.58.14.1 or later
- If running version 1.59.x, upgrade to version 1.59.10 or later
- If running version 1.60.x, upgrade to version 1.60.4 or later
- After upgrade, review database connection configurations to ensure no malicious JDBC parameters were added
- Consider restricting database connection configuration permissions to trusted admins only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50147 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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