Executive Summary
A maximum-severity zero-day vulnerability (CVSS 10.0, currently unassigned CVE) impacting the widely deployed Metabase business intelligence and data visualization platform is being actively exploited in the wild. The security flaw allows unauthenticated remote attackers to execute arbitrary SQL injection queries against the underlying Metabase application database.
By gaining administrative privileges on affected instances, threat actors can alter system configurations, exfiltrate stored database credentials, and read or dump sensitive enterprise data. Confirmed breaches at online form platform Tally Forms, AI coding vendor Kilo Code, and hardware maker Framework highlight the urgent need for self-hosted instances to apply emergency vendor patches.
Deep-Dive Technical Analysis
Metabase serves as a core analytics layer, connecting directly to enterprise SQL databases and data warehouses to allow teams to query business data. The zero-day vulnerability impacts Metabase versions 1.58 and above across both open-source and paid deployment tiers.
Attack Vector and Execution Chain
* Unauthenticated Entry: The flaw exists within an unauthenticated API endpoint in the Metabase web application layer. The endpoint fails to sanitize user-supplied input parameters before concatenating them into raw SQL queries directed at the application's internal database (PostgreSQL/H2/MySQL).
* Privilege Escalation: By injecting malicious SQL syntax, remote threat actors bypass authentication checks and elevate their privileges to full Administrator status within the Metabase application layer.
* Credential Harvesting: Once administrative access is established, attackers leverage Metabase's credential store. Metabase securely holds connection strings, API keys, and database passwords used to query connected data warehouses (e.g., Snowflake, BigQuery, AWS Redshift, PostgreSQL). The exploit allows threat actors to decrypt or dump these connection credentials.
* Data Exfiltration: Threat actors use the harvested credentials or built-in Metabase export features to dump customer records, hashed passwords, and OAuth/Slack tokens. Known impact includes Tally Forms (customer email directories and password hashes) and Kilo Code (names, emails, and active Slack access tokens).
Industry Impact and Recommendations/Mitigations
The exploitation of business intelligence tools presents severe supply-chain risks, as a single Metabase instance often sits at the nexus of multiple corporate production databases.
Immediate Action Plan & Mitigations
Action Category
Mandatory Mitigation Steps
Patching
Immediately update all self-hosted Metabase instances to patched releases (v1.58.x patched builds or latest production releases).
Credential Security
Assume all database credentials, connection strings, and integration tokens have been exposed. Rotate all database passwords and invalidate connected OAuth/Slack access tokens.
Network Security
Restrict internet access to self-hosted instances using web application firewalls (WAF), IP whitelisting, or VPN/zero-trust access gateways.
Incident Response
Inspect Metabase application access logs for unusual SQL execution patterns, unauthorized administrator creation, or bulk data export requests.
Authorized by: Person
Date of Issue: Date