Metabase SQL Injection Zero-Day Grants Attackers Full Admin Access

A critical zero-day SQL injection vulnerability in the Metabase business intelligence platform has been exploited by attackers to gain full administrative control over affected instances. The flaw allows unauthenticated remote actors to bypass security controls and access sensitive backend data, posing a severe risk to organizations using the software for data visualization.

The vulnerability, identified as CVE-2026-72898, affects Metabase versions 1.58 and above. Attackers can exploit the flaw by injecting malicious SQL via the '/api/session/reset_password' endpoint. Once successful, the attacker gains full administrator access to the instance, enabling them to steal database credentials, modify system configurations, and export sensitive data from connected downstream databases. Due to the severity of the exploit, it has been assigned a maximum CVSS score of 10.0.

The Root of the Breach

Metabase functions as a front-end interface for a wide variety of SQL databases, meaning the platform often stores high-privilege credentials to access core business data. The vulnerability stems from a failure to use prepared statements within the password reset functionality. This is a critical security oversight in software designed to support diverse database types, as it allows user-supplied input to be executed as code by the underlying database engine.

Industry Impact and Blast Radius

The "blast radius" of this vulnerability is exceptionally wide because a single compromise of a Metabase instance provides a direct path to the sensitive data stored in multiple connected backend sources. The breach has already impacted both SaaS (Metabase Cloud) and self-hosted environments. Confirmed victims include Framework—where the attack affected all customers—as well as Tally and Kilo Code.

According to Metabase CEO Sameer Al-Sakran, the company responded by immediately blocking the endpoints used for the attack before identifying and patching the vulnerability. The incident underscores the danger of centralized BI tools that hold "keys to the kingdom" for an organization's entire data infrastructure.

What's Next

Organizations running Metabase versions 1.58 or later are urged to update to the latest patched version immediately to close the injection vector. Security teams should also audit their database logs for unauthorized exports or credential changes originating from the Metabase service account. While the primary vulnerability has been addressed, the full extent of the data exfiltrated from the confirmed victims remains under investigation.