Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-50147: Metabase is an open-source business intelligence and embedded analytics tool

33
Routine
HIGH 7.6UPGRADE

CVE-2026-50147 is a high-severity flaw (CVSS 7.6) affecting metabase. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 da

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.6 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.3% (top 73%)
CISA exploited listNo
WeaknessCWE-88
Published2026-07-15
Last modified2026-07-30
Publisher (CNA): GitHub, Inc. · Vendor: metabase

Share: LinkedIn · X · Reddit

Last updated 2026-07-30 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

metabase metabase UPGRADE
Affected: >= 1.57.0 and < 1.57.19.1 · >= 1.58.0 and < 1.58.14.1 · >= 1.59.0 and < 1.59.10 · >= 1.60.0 and < 1.60.4
Fixed in: 1.57.19.1, 1.58.14.1, 1.59.10, 1.60.4
Safe to downgrade to: a release before 1.57.0
1. Check installed version
apt-cache policy metabase || rpm -q metabase || metabase --version
2. UPGRADE to 1.57.19.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade metabase
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade metabase
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.57.0 (Debian / Ubuntu)
apt-cache madison metabase sudo apt install metabase=<VERSION_BEFORE_1.57.0> sudo apt-mark hold metabase
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list metabase sudo dnf downgrade metabase-<VERSION_BEFORE_1.57.0> sudo dnf versionlock add metabase
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-50147?

metabase: upgrade to 1.57.19.1, 1.58.14.1, 1.59.10, 1.60.4. Exact commands for each OS are on this page.

Is CVE-2026-50147 being exploited?

CVE-2026-50147 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-50147 affect?

CVE-2026-50147 affects metabase. Severity is high (CVSS 7.6). 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 Metaba

How urgent is CVE-2026-50147?

Priority 33/100. High severity

Software pages

MySQL vulnerabilities · MariaDB vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.