Business intelligence platform provider Metabase disclosed a zero-day SQL injection vulnerability on August 6 that allowed attackers to gain direct SQL access to its underlying database, potentially exposing customer credentials, API keys, and other sensitive information. The flaw, tracked as CVE-2026-72898 and affecting versions 1.58 and up, received a severity score of 10 out of 10—the highest possible rating under the Common Vulnerability Scoring System. Metabase said a threat actor exploited the vulnerability through the /api/session/reset_password endpoint before the company blocked access, deployed patches, and revoked compromised credentials.

The vulnerability's reach is substantial: search engine Shodan has identified approximately 2,500 Metabase instances worldwide, while security firm Wiz reported that roughly 13% of cloud environments run self-hosted Metabase deployments, with about a quarter of those fully accessible from the internet. Organizations confirmed as impacted so far include Kilo Code, recently purchased by Anaconda; Y Combinator-backed Tally; personal computer maker Framework; workflow automation provider n8n; and AI monitoring platform ChecklyHQ. Compromised records contained usernames, email addresses, cloud passwords, cryptographic hashes of OpenTelemetry API keys for trace collection, Slack access tokens, and additional sensitive data. Metabase Cloud customers have already received patches, but self-hosted users remain at risk unless they've upgraded.

According to Metabase's disclosure, organizations can identify a breach by looking for a specific pattern in their logs: a POST call to /api/session/reset_password showing a 400 status code, followed by a GET call to /api/user/current returning a 200 status code. "If you find that pattern in your application logs or in your Metabase server ingress logs, it is likely that your instance has been compromised," the company warned. Scott Miserendino, CTO at DataBee, explained that the flaw grants attackers "unmitigated, raw SQL access to the Metabase database," allowing them to steal or modify account credentials for connected databases, create new administrator accounts, alter app configurations, raise privileges, or "degrade, alter or destroy" information.

The vulnerability's impact extends beyond organizations that knowingly use Metabase. Miserendino cautioned that the flaw also affects platforms running original equipment manufacturer versions of Metabase as part of their infrastructure, meaning affected users may not realize they're vulnerable because they don't know Metabase powers a product they purchased. Customers unable to upgrade immediately can temporarily block the /api/session/reset_password endpoint, though Metabase urges moving to patched versions—for instance, users on version 0.58.6 should upgrade to 0.58.24 or later. If the vulnerable endpoint was publicly accessible, organizations should revoke all active user sessions, review and delete unrecognized API keys, audit data warehouse logs and admin accounts for unauthorized access, rotate credentials for connected databases, and examine Metabase activity histories. ChecklyHQ acknowledged the incident's broader lesson in its customer notice: "Rotating credentials fixes the immediate problem. It does not fix the reason this hurt: Our analytics environment held more sensitive data and had broader access than it needed." SQL injection vulnerabilities remain deceptively dangerous precisely because they blend familiarity with catastrophic potential—when analytics tools sit at the crossroads of every database an organization trusts, a single endpoint can unravel the entire security perimeter.