A maximum-severity, unauthenticated SQL injection zero-day in the popular open-source analytics platform Metabase has been actively exploited in the wild, letting attackers seize administrator privileges and steal credentials for every database connected to compromised instances.
Metabase disclosed that its Cloud infrastructure was targeted starting around August 3, 2026, when attackers weaponized a previously unknown flaw affecting self-hosted and cloud deployments running version 1.58.
The vulnerability, tracked as GHSA-vwf4-m7j8-wcjf and rated CVSS 10.0, resides in the unauthenticated POST /api/session/reset_password endpoint.
Metabase Zero-Day Attack
No CVE identifier had been assigned at the time of disclosure, meaning scanners relying solely on NVD feeds will not flag exposed instances. By sending crafted input to the password-reset endpoint, a remote attacker with no credentials can inject arbitrary SQL into Metabase’s application database.
This grants full administrator access to the instance, allowing attackers to alter application configuration, harvest stored credentials for every connected data source, read accessible data, and export it in bulk.
Metabase confirmed active exploitation against its Cloud environment before patching and blocking the abused endpoints.
Reported victims include Framework and Tally customers, where unauthorized access reportedly exposed customer records such as names, emails, addresses, phone numbers, and company details.
Metabase Cloud has since been fully patched, but self-hosted instances remain at risk until administrators manually upgrade.
Defenders should scan application and ingress logs for a distinctive two-step pattern that signals likely exploitation: a POST request to /api/session/reset_password returning a 400 status code, immediately followed by a GET request to /api/user/current returning a 200 status code.
Instances that show this sequence in their logs should be treated as compromised and escalated to incident response.
Affected Versions and Fixes
Vulnerable branches span 0.58.0 through 0.63.x, along with equivalent 1.x releases; versions below 58 are not affected.
Patched minimum-safe releases are 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5, all available as Docker images tagged with their respective version numbers or as downloadable JAR files from Metabase’s official release channels.
Administrators should identify their current version through the “About Metabase” panel and upgrade to the corresponding safe release without delay.
Mitigation
Organizations running self-hosted Metabase should upgrade immediately to the minimum safe version for their branch.
If the reset_password endpoint has been publicly reachable, responders should revoke all active sessions by clearing the core_session table, audit API keys, and remove any unrecognized entries; review administrator accounts for unexpected changes.
Where immediate patching isn’t feasible, organizations can temporarily block all traffic to the reset_password endpoint as a stopgap measure.
This incident, which maps to MITRE ATT&CK techniques including Exploit Public-Facing Application, Account Manipulation, and Trusted Relationship abuse, underscores the outsized risk that unauthenticated endpoints on internet-facing business intelligence platforms pose to downstream data infrastructure and connected systems.
Detect, investigate, and respond faster with in-browser data inspection from ANY.RUN. Gain complete phishing visibility to strengthen your SOC and reduce MTTR
