CVE-2026-50147

Metabase: Arbitrary File Read via MySQL Connection Property Injection

Published Jul 15, 2026 CVSS 3.1 · 7.6 High EPSS < 1% KEV · Not listed
Description
Metabase 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.

Analysis

AI-generated

Technical impact

Metabase, an open‑source business intelligence and embedded analytics platform, permits users to configure database connections. In versions 1.57.0 through 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4, an attacker who can create or modify a MySQL or MariaDB connection can inject unsafe JDBC parameters into the connection string. The JDBC driver interprets these parameters as file paths, causing it to read arbitrary files from the Metabase host. The contents of those files are then exposed through query results or validation error messages. This flaw, classified under CWE‑88, enables read‑only access to any file that the Metabase process can read.

Affected Systems

All installations of Metabase from version 1.57.0 through 1.57.19.1, 1.58.14.1, 1.59.10, or 1.60.4 are affected. The vulnerability is mitigated by upgrading to the fixed releases 1.57.19.1, 1.58.14.1, 1.59.10, or 1.60.4.

Risk and Exploitability

The CVSS score of 7.6 signals a high‑severity flaw, but the EPSS score of less than 1 % indicates that exploitation is currently unlikely. The vulnerability is not listed in the CISA KEV catalog. The attack vector can be inferred to be a local configuration privilege: an attacker must be able to add or alter MySQL/MariaDB connections in Metabase. Once that condition is met, the attacker can read any file that the Metabase process is allowed to access, potentially exposing sensitive configuration or source code.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Metabase version 1.57.19.1, 1.58.14.1, 1.59.10, or 1.60.4 to apply the vendor fix.
  • Restrict the creation or modification of database connections to users with administrative rights only.
  • Validate or sanitize JDBC connection parameters to reject or treat values that could be interpreted as file paths.

Generated by OpenCVE AI on July 31, 2026 at 03:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Metabase
Metabase metabase
Vendors & Products Metabase
Metabase metabase
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Metabase 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.
Title Metabase: Arbitrary File Read via MySQL Connection Property Injection
Weaknesses CWE-88
References
Metrics cvssV3_1

{'score': 7.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N'}

Weaknesses
  • CWE-88

    Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 4:04 PM
Reserved
Jun 3, 2026, 6:49 PM
Status
Analyzed
Published
Jul 15, 2026, 4:16 PM
Modified
Jul 30, 2026, 2:30 PM