Executive Summary
A maximum-severity zero-day vulnerability in the Metabase cloud business intelligence (BI) platform has been exploited in the wild, triggering data breaches across several notable technology and SaaS organizations. Affected victims include repairable hardware maker Framework, online form provider Tally Forms, and AI coding platform Kilo Code. The zero-day SQL injection flaw allows unauthenticated remote attackers to execute arbitrary SQL commands directly against the underlying Metabase application database, granting full administrative control and facilitating stealthy exfiltration of customer records, password hashes, and active authentication tokens.
Technical Deep-Dive & Attack Mechanics
Metabase is an open-source and cloud-based data visualization suite widely deployed by enterprises to connect internal databases and run analytical queries. On August 6, 2026, Metabase confirmed that an unauthenticated remote attacker exploited a zero-day SQL injection flaw impacting Metabase version 58 and above.
The flaw stems from improper sanitization of user-supplied input parameters within Metabase's cloud-hosted backend API endpoints. By crafting malicious SQL payloads, unauthenticated attackers were able to bypass application authentication barriers and execute arbitrary SQL queries against Metabase's core metadata repository.
This level of access enabled threat actors to:
* Bypass Authentication Boundaries: Elevate privileges to full Metabase Instance Administrator without valid credentials.
* Access Data Catalogs: Query connected operational databases and exfiltrate connected customer datasets.
* Harvest Sensitive Credentials: Exfiltrate user metadata, hashed passwords, contact details, and third-party API keys (including live Slack access tokens in Kilo Code's infrastructure).
Victim Organization
Description
Confirmed Data Impact
Framework
Repairable hardware maker
Names, physical addresses, emails, phone numbers, login IP logs
Kilo Code
AI coding platform
Live Slack access tokens, infrastructure-linked API keys
Tally Forms
Online form provider
General data breach involvement
In response, affected organizations rotated database credentials, invalidated compromised Slack session tokens, and applied upstream Metabase security patches.
Industry Impact & Strategic Mitigation
The Metabase zero-day breach highlights the extreme supply-chain risk posed by centralized analytics and BI platforms, which often sit at the intersection of multiple critical corporate databases.
Key Risk Considerations
* Supply-Chain Exposure: A single unpatched flaw in an aggregated analytics tool grants attackers access across all linked data stores.
* Third-Party API Token Abuse: Stolen API tokens (e.g., Slack, cloud infrastructure) allow threat actors to pivot deeper into corporate communications and CI/CD pipelines.
Recommendations & Defense Actions
* Immediate Upgrade: Self-hosted and cloud Metabase customers must immediately verify that instances are running patched builds above version 58.
* Credential & Token Rotation: Rotate all database passwords, service account credentials, and OAuth tokens connected to or managed within Metabase instances.
* Database Privilege Segregation: Restrict BI service account database permissions to read-only access and restrict network connections using strict firewall rules or private VPC endpoints.
* Monitoring & Auditing: Audit database access logs for unusual high-volume SQL exports or administrative user creation events originating from BI IP ranges.