CVE-2026-72898: Unauthenticated SQL Injection in Metabase Password-Reset API
- Vendor
- Metabase
CVE-2026-72898 is a critical unauthenticated blind SQL injection vulnerability in Metabase's password-reset API. Vulnerable authentication processing merges request data with authentication results, retaining an attacker-controlled user-id value when authentication does not supply one. A structured user-id containing HoneySQL's :raw directive subsequently reaches a t2/select-one query and is interpreted as literal SQL rather than parameterized input. This permits arbitrary SQL execution against Metabase's application database and can provide administrator access. The vulnerability affects unpatched Open Source 0.58–0.63 branches and corresponding Enterprise 1.x branches; releases before branch 58 are unaffected. The fix validates that user-id is a positive integer before querying. Metabase disclosed the vulnerability on August 6, 2026, following zero-day exploitation against Metabase Cloud.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise Metabase application data and administrator accounts, exposing saved queries, configuration, API keys, and credentials for connected databases. Attackers can read or export accessible business data and potentially modify application state or disrupt service. Observed exploitation included unauthorized administrator creation, data theft, and extortion. Operating-system command execution is possible in deployments with sufficiently privileged database connections, including PostgreSQL connections permitted to execute server-side programs; this is a conditional downstream consequence, not an inherent outcome on every installation.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrading is impossible, temporarily block access to /api/session/reset_password. Restrict Metabase network accessibility to authorized users and remove unnecessary public exposure. Apply least privilege to application-database and connected-database accounts; PostgreSQL accounts should not have superuser access or unnecessary pg_execute_server_program privileges. Monitor for suspicious password-reset requests, unexpected administrator accounts, API keys, sessions, database-connection changes, unusual queries, exports, and server processes spawning shells.
Remediation
Patch, then assume compromise.
Upgrade immediately to the latest supported Metabase release. Initial fixes for this CVE were Open Source versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5, with corresponding Enterprise versions using the 1.x prefix. Subsequent security guidance raised minimum safe releases to 0.58.31, 0.59.28, 0.60.24, 0.61.18, 0.62.16, and 0.63.13, respectively, or their Enterprise equivalents, to address additional vulnerabilities. For previously exposed installations, revoke active sessions, investigate administrator changes and unrecognized API keys, rotate connected-database credentials, and review Metabase activity, query history, and database or warehouse logs. Patching alone does not remove access already established by an attacker.
Exploits
7 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-72898 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 11, 2026.
- Is there a public exploit for CVE-2026-72898?
- Yes. Mallory tracks 7 public exploits or proofs of concept for CVE-2026-72898, the earliest disclosed Aug 15, 2026.
- Is there a patch for CVE-2026-72898?
- Upgrade immediately to the latest supported Metabase release. Initial fixes for this CVE were Open Source versions 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5, with corresponding Enterprise versions using the 1.x prefix.
- What products are affected by CVE-2026-72898?
- Metabase.
- How severe is CVE-2026-72898?
- CVE-2026-72898 has a CVSS v4 score of 10.0 (Critical) and an EPSS score of 98.5% (100th percentile) as of Nov 17, 2026.
Recent activity
141 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.