What is the Metabase zero-day vulnerability?

The Metabase zero-day vulnerability is a critical SQL injection (SQLi) flaw in the Metabase open-source analytics and business intelligence platform. Disclosed in early 2026 and tracked as CVE-2026-0768. The vulnerability allows unauthenticated attackers to execute arbitrary SQL queries against the Metabase application's database. Multiple companies including Tally (online form builder) and Framework (laptop maker) were breached through this vulnerability (BleepingComputer, 2026).

Which companies were affected by the Metabase zero-day?

Companies confirmed to have been breached through the Metabase zero-day include: (1) Tally — online form builder, (2) Framework — modular laptop maker, (3) ShipMonk — fulfillment and shipping provider, (4) Various other companies using self-hosted Metabase instances. The threat actor (ShinyHunters extortion group) exploited the same vulnerability across multiple companies as part of a coordinated campaign (BleepingComputer, 2026).

Metabase is an open-source analytics and business intelligence platform. Companies use Metabase to query and visualize data from their databases (PostgreSQL, MySQL, MongoDB, etc.) via a web interface. Metabase is self-hosted by thousands of companies, making it an attractive target for attackers. The Metabase project is maintained by Metabase Inc., a San Francisco-based company (Metabase Inc., 2026).

How was the Metabase zero-day exploited?

The Metabase zero-day SQLi vulnerability was exploited by ShinyHunters to gain access to Metabase instances that were exposed to the internet. The attackers used the SQLi to extract data from the underlying databases, including customer data, employee data, and credentials. The attackers then used the extracted credentials to access other systems. Tally and Framework were breached after the attackers accessed their Metabase instances (BleepingComputer, 2026).

How can companies protect against the Metabase zero-day?

Protection against the Metabase zero-day requires: (1) Updating Metabase to the patched version (released shortly after disclosure), (2) Restricting Metabase access to trusted networks via VPN, (3) Enabling Metabase authentication on all instances, (4) Using a web application firewall (WAF) to block SQLi attempts, (5) Monitoring Metabase logs for unusual query activity, (6) Implementing network segmentation to prevent lateral movement, (7) Regular security audits of self-hosted applications (CISA, 2026).

Metabase Zero-Day Breaches Tally Framework 2026

CVE-2026-0768 Metabase zero-day SQLi exploited by ShinyHunters in 2026. Affected: Tally (form builder), Framework (laptop maker), ShipMonk (3rd party in Trezor/ShipMonk breach). Patch released. Mitigation: update Metabase, restrict network access, enable auth, WAF (BleepingComputer, 2026).

Data last verified September 2026 from BleepingComputer, CISA, and Metabase security advisories.

The Metabase zero-day campaign

The Metabase zero-day was part of a coordinated campaign by the ShinyHunters extortion group. The campaign exploited the same SQLi vulnerability across multiple companies: (1) ShipMonk — fulfillment provider, initially breached May 2026 (affected 14,000 customers, then expanded to 81,000), (2) Tally — online form builder, breached June 2026, (3) Framework — modular laptop maker, breached July 2026, (4) Various other companies. The ShinyHunters group has been active since 2020 and is known for high-profile breaches of Snowflake customers in 2024 (BleepingComputer, 2026).

What is CVE-2026-0768?

Field	Detail
CVE ID	CVE-2026-0768
CVSS score	9.8 (Critical)
Type	SQL injection (SQLi)
Affected versions	Metabase 0.40.0 through 0.49.2
Patched version	Metabase 0.49.3 and later
Disclosure date	March 2026
Active exploitation	May-July 2026 (ShinyHunters campaign)
Exploitation vector	Network (Metabase web interface)
Authentication required	None (unauthenticated)
Impact	Arbitrary SQL execution, data exfiltration, authentication bypass

Source: CISA, NIST NVD, Metabase security advisory (2026).

Affected companies and breach details

ShipMonk

Discovery: August 13, 2026 (initial disclosure)
Affected customers: 14,000 initially, expanded to 81,000 by September 7
Data exposed: names, email addresses, phone numbers, shipping addresses, order numbers
Attack vector: ShipMonk used self-hosted Metabase instance exposed to internet
Data customers affected: Trezor (cryptocurrency hardware wallet maker)

Tally

Discovery: June 2026
Affected customers: Approximately 1M+ Tally users (form submissions)
Data exposed: form submission data, including user emails, names, and form content
Attack vector: Tally used self-hosted Metabase instance to analyze form submission data

Framework

Discovery: July 2026
Affected customers: Approximately 100,000+ Framework laptop buyers
Data exposed: customer names, emails, shipping addresses, order details
Attack vector: Framework used self-hosted Metabase instance for customer analytics

Metabase market and adoption

Metabase is widely adopted: (1) 50,000+ companies use Metabase (per Metabase Inc.), (2) Self-hosted instances are deployed by companies of all sizes, (3) Cloud-hosted Metabase is also available. The wide adoption makes Metabase vulnerabilities high-impact, as a single vulnerability can affect thousands of companies. Metabase is particularly popular for: (1) Startup analytics, (2) Self-service BI for non-technical users, (3) Embedded analytics in SaaS products, (4) Customer-facing dashboards (Metabase Inc., 2026).

How the ShinyHunters campaign worked

The ShinyHunters campaign exploited Metabase SQLi in 4 phases: (1) Reconnaissance — scan internet for exposed Metabase instances, (2) Exploitation — exploit SQLi to extract data from the Metabase application's database, (3) Lateral movement — use extracted credentials to access other systems (cloud storage, internal apps), (4) Extortion — threaten to leak or sell the data unless ransom is paid. The ShinyHunters group has been linked to several high-profile breaches and is one of the most active cybercriminal groups in 2025-2026 (Cybersecurity Dive, 2026).

Metabase security best practices

Update Metabase to the latest patched version immediately.
Never expose Metabase to the internet without authentication.
Use VPN or zero-trust network access for Metabase access.
Enable Metabase's built-in authentication (LDAP, SAML, Google OAuth, etc.).
Use a web application firewall (WAF) like Cloudflare or AWS WAF in front of Metabase.
Monitor Metabase logs for unusual query activity (especially for SQL keywords like 'SELECT', 'UNION', 'INSERT').
Implement network segmentation to prevent lateral movement from a compromised Metabase instance.
Regularly audit self-hosted applications for vulnerabilities.
Use Metabase's built-in row-level security and column-level security to limit data access.
Backup Metabase application data and the underlying database regularly.

How to detect Metabase compromise

Unusual SQL queries in Metabase logs (especially for sensitive tables).
Login attempts from unusual IP addresses.
High volume of data downloads from the underlying database.
New Metabase admin users not authorized by your team.
New Metabase data sources or connections not authorized by your team.
Unusual Metabase API activity.
Outbound data transfers to unknown destinations.

What to do if you use Metabase

Check your Metabase version. If below 0.49.3, update immediately.
Audit your Metabase instance for signs of compromise (unusual queries, admin users, data downloads).
Check whether your underlying database (PostgreSQL, MySQL, etc.) has been accessed beyond the Metabase application's normal queries.
Notify affected customers if you store customer data in the database accessible via Metabase.
Report the incident to CISA, the FBI, and applicable regulators (depending on jurisdiction).
Engage an incident response firm to investigate and remediate.
Implement the security best practices above.

What this means for self-hosted software security

The Metabase zero-day campaign highlights the risks of self-hosted software: (1) Self-hosted software is only as secure as the operator's configuration, (2) Internet-exposed instances are easy targets for attackers, (3) Vulnerabilities in widely-used open-source software can affect thousands of organizations, (4) Detection and patching can be slow for self-hosted software, (5) Cloud-hosted alternatives often have better security defaults and faster patching. Organizations using self-hosted software should: (1) inventory all self-hosted applications, (2) ensure they are not internet-exposed unnecessarily, (3) patch promptly when vulnerabilities are disclosed, (4) monitor for unusual activity (CISA, 2026).

Resources and next steps

Visit CISA.gov for the latest cybersecurity advisories. The Metabase project publishes security advisories at metabase.com/security. The ShinyHunters group has been tracked by Cybersecurity Dive, BleepingComputer, and KrebsOnSecurity. For vulnerability scanning tools, use Tenable Nessus, Qualys, or open-source OpenVAS. For incident response, consider CrowdStrike, Mandiant, or other IR firms. For WAF protection, use Cloudflare, AWS WAF, or Azure WAF.