The Metabase zero-day: how a password-reset endpoint becomes a BI data exfiltration route
On August 6, 2026, Metabase disclosed that a maximum-severity SQL injection vulnerability had been exploited as a zero-day against Metabase Cloud. The bug received a CVSS score of 10.0: the highest possible.
As of noon UTC on August 10, public proof-of-concept exploit code is live. Framework and Tally have both confirmed breaches. If your organization runs a self-hosted Metabase instance, the threat window is now fully open.
What the vulnerability actually is
The root cause is a SQL injection flaw in the /api/session/reset_password endpoint. This endpoint exists to let users reset their passwords. It requires no authentication. An attacker sends a crafted request and injects arbitrary SQL into the Metabase application database, eventually gaining administrator-level access to the instance.
From that position, the attacker can read, modify, or export any data the Metabase instance can reach: every connected database and every query result stored on the platform.
The flaw is tracked as GHSA-vwf4-m7j8-wcjf. It affects every Metabase release from version 58 through version 63, covering both the hosted cloud product and all self-hosted installations. Patched releases: x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, and x.63.5.
Why BI tools are a high-value target
Business intelligence platforms sit at a unique position in an organization's data architecture. They connect to production databases, data warehouses, and analytics pipelines. They store connection credentials. They retain query histories. A single compromised Metabase instance can expose data from dozens of upstream systems that were never intended to be publicly accessible.
The attack path here is particularly blunt: no account required, no phishing required, no social engineering required. One HTTP request to a password-reset endpoint and an attacker is looking at your data. For organizations running Metabase connected to customer databases, financial systems, or health records, the blast radius of an unpatched instance is significant.
What you should do
Patch immediately. If you run Metabase Cloud, hosted instances were patched directly and you are protected. If you run a self-hosted instance, apply the update now. Public exploit code is available and mass-exploitation attempts are a present reality, not a future risk.
After patching, review your Metabase instance logs for anomalous requests to /api/session/reset_password. Audit what databases and data sources are connected. Rotate any credentials stored in Metabase's connection configuration. If you ran an unpatched instance between August 6 and today, treat your connected databases as potentially compromised and review their access logs as well.
Gigia Tsiklauri is a Security Architect and founder of Infosec.ge. Get in touch if you are assessing exposure in your BI stack.