Which versions of Metabase are affected by CVE-2026-72900?

Metabase contains an authorization bypass vulnerability (CVE-2026-72900) that allows any registered user to read the entire backend database, including connection credentials and API keys.

How to fix or mitigate CVE-2026-72900?

Within 24 hours: audit Metabase access logs for unauthorized database queries, immediately restrict network access to Metabase to essential administrators only, and rotate all database connection credentials and API keys that may be exposed in Metabase. Within 7 days: contact Metabase vendor support to confirm affected versions and patch timeline, evaluate migration to alternative analytics platforms if Metabase is not mission-critical, and document which systems could be compromised via exposed credentials. Within 30 days: implement a reverse proxy with additional authentication (MFA) in front of Metabase, complete credential rotation for all systems that connect to or are referenced in Metabase, and commit to either waiting for a vendor patch (with timeline) or migration to an alternative platform.

Metabase CVE-2026-72900

Q: What is the CVSS score of CVE-2026-72900?

CVE-2026-72900 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-55692 HIGH

Missing Authorization (CWE-862)

2026-08-10 cisa-cg

Authentication Bypass Metabase

7.1

CVSS 4.0 · Vendor: cisa-cg

Severity by source

Vendor (cisa-cg) PRIMARY

7.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.5 MEDIUM

Network-reachable, low complexity; low privileges required (authenticated user); no integrity or availability impact; full confidentiality loss of application database.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (cisa-cg).

CVSS VectorVendor: cisa-cg

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 10, 2026 - 18:36 vuln.today

Severity Changed

Aug 10, 2026 - 18:22 NVD

MEDIUM HIGH

CVSS changed

Aug 10, 2026 - 18:22 NVD

6.5 (MEDIUM) 7.1 (HIGH)

CVE Published

Aug 10, 2026 - 17:56 cve.org

HIGH 7.1

DescriptionCVE.org

Metabase allows an authenticated, low-privileged attacker to read the entire Metabase application database.

AnalysisAI

Full application database read in Metabase is achievable by any authenticated low-privileged user due to a missing authorization check (CWE-862). Any user with a valid account - regardless of their assigned role or permissions - can issue requests that return the entire contents of the Metabase backend database, potentially exposing database connection credentials, API keys, user account data, and sensitive query results. No public exploit has been identified at time of analysis, but the low exploitation complexity and broad attacker pool (any registered user) make this a high-priority remediation item.

Technical ContextAI

Metabase is an open-source business intelligence and analytics platform widely used to connect to enterprise databases, build dashboards, and share data queries. The affected CPE (cpe:2.3:a:metabase:metabase:*:*:*:*:*:*:*:*) covers all tracked versions of the core Metabase application. CWE-862 (Missing Authorization) indicates that Metabase fails to verify whether the requesting user has permission to access certain data-retrieval endpoints or internal APIs before executing them. This is distinct from authentication bypass (where auth is skipped entirely); here authentication occurs, but the authorization layer that should restrict low-privileged users from accessing the full application database is absent or incomplete. The Metabase application database typically stores connection strings to upstream data sources, user credentials, session tokens, and internal configuration - making its full disclosure especially severe.

RemediationAI

The primary remediation is to apply the vendor-issued patch referenced in the GitHub Security Advisory GHSA-8hmm-hrhg-ppqp (https://github.com/metabase/metabase/security/advisories/GHSA-8hmm-hrhg-ppqp). An exact fixed version is not independently confirmed from the provided data - consult the advisory directly to identify the minimum safe release and upgrade to it immediately. As a compensating control while patching is underway, restrict access to Metabase to only trusted, explicitly authorized users by auditing and pruning low-privileged accounts; disable self-registration if enabled, since any valid account qualifies as an attacker. Network-level controls (placing Metabase behind a VPN or requiring client-certificate authentication at a reverse proxy layer) can reduce the exposed attacker surface but do not remediate the underlying missing authorization flaw. Review Metabase application database contents for exposed connection strings and rotate any credentials stored there as a precautionary measure regardless of whether exploitation is confirmed.