Metabase Zero-Day SQL Injection Exploited in the Wild to Access Cloud Customer Data
Executive Summary
A critical zero-day vulnerability in Metabase, the popular open-source business intelligence and data visualization platform, is being actively exploited in widespread attacks targeting both self-hosted and cloud-hosted instances. Disclosed in August 2026, the zero-day unauthenticated SQL injection vulnerability affects Metabase version 58 and above. Multiple technology companies—including online form provider Tally Forms and AI coding platform Kilo Code (Anaconda)—have confirmed security incidents where threat actors exploited the Metabase zero-day to breach application databases, exfiltrate user credentials, password hashes, and active Slack integration access tokens.
Deep-Dive Technical Analysis
The Vulnerability: Metabase Unauthenticated SQL Injection
* Vulnerability Type: Unauthenticated Remote SQL Injection.
* Affected Versions: Metabase Open-Source and Enterprise Edition versions 58.x and higher.
* Root Cause: Inadequate parameterization and input sanitization within an unauthenticated API endpoint used during initial setup/telemetry or session initialization routines in Metabase v58.
* Exploitation Mechanics: An unauthenticated remote attacker issues a specially crafted HTTP request containing SQL injection payloads directly to the vulnerable Metabase web interface. The injected SQL commands execute within the application database context with the privileges of the Metabase service account.
* Impact & Post-Exploitation: By injecting arbitrary SQL, attackers can bypass administrative password checks, extract the master encryption keys stored in Metabase's application database, create persistent super-admin accounts, and query all connected underlying data warehouses (PostgreSQL, MySQL, Snowflake, BigQuery) linked to the Metabase instance.
Confirmed Customer Data Breaches
1. Tally Forms: Confirmed an intrusion originating from their Metabase deployment. Threat actors exfiltrated user account records including registered email addresses and hashed passwords.
2. Kilo Code (Anaconda): Reported that attackers leveraged the Metabase zero-day to exfiltrate user names, email addresses, and active Slack OAuth access tokens. Kilo Code immediately revoked all impacted Slack tokens to prevent unauthorized workspace access.
Industry Impact and Recommendations/Mitigations
Because Metabase acts as a central aggregation hub connecting sensitive corporate databases for analytics, zero-day vulnerabilities in BI tools pose an acute risk to corporate confidential data.
Recommended Actions for Security Teams:
1. Emergency Software Upgrade: Immediately apply the latest emergency vendor security patch released by Metabase for all self-hosted and on-premises instances. Ensure cloud instances managed internally are verified.
2. Credential and Secret Revocation:
* Invalidate all API keys, database connection strings, and OAuth access tokens (e.g., Slack, Google, GitHub) stored within Metabase configuration settings.
* Force a global password reset for all Metabase administrative and user accounts.
3. Database Audit & Isolation: Review database query logs on all underlying data stores linked to Metabase for unusual SELECT queries or bulk data exports executed during the vulnerability window (August 1–11, 2026).
4. Network Perimeter Defense: Restrict access to Metabase management portals behind VPNs or Zero-Trust Network Access (ZTNA) gateways rather than exposing them directly to the public internet.