Framework, a San Francisco-based laptop manufacturer, has confirmed a data breach stemming from a zero-day vulnerability in the Metabase business intelligence service. The incident led to unauthorized access to customer names, email addresses, phone numbers, physical addresses, and login IP addresses. Framework clarified that payment information and order records were not compromised.
The company was alerted to the breach by Metabase, which confirmed that attackers had gained access to Framework's cloud instance of the service. In response, Framework has rotated credentials for all databases connected to its Metabase instance and stated that it has not found evidence of a broader system compromise. Customers affected by the breach have been advised to remain vigilant against potential phishing attempts.
The zero-day vulnerability, a critical SQL injection flaw, affects Metabase versions 58 and above. It allows an unauthenticated remote attacker to inject arbitrary SQL into the Metabase application database, potentially granting them administrator access to the instance. With administrative access, an attacker could modify application configurations, exfiltrate stored credentials for connected databases, read any data accessible via those connections, and export data.
Metabase, a business intelligence tool, is used by companies to analyze their business data. It offers both a free open-source version for self-hosting and paid service plans that include cloud and self-hosted options. The company behind Metabase disclosed on August 6, 2026, that its Metabase Cloud service had been targeted via this SQL injection vulnerability, which currently lacks a CVE identifier.
Beyond Framework, other companies have also reported breaches through the same Metabase vulnerability. Tally, a Belgian online form-building platform, notified users that their email addresses and password hashes were accessed. Kilo Code, an AI coding platform now owned by Anaconda, reported that customer names, emails, and Slack access tokens were compromised, though the Slack tokens were immediately invalidated.
Metabase has released fixes for all affected versions and urged self-hosting customers to upgrade promptly. Additionally, Metabase recommended that users revoke active sessions, review API keys and administrator accounts, rotate credentials, examine data warehouse logs for unauthorized access, and scrutinize Metabase activity and query history for any unexpected or unauthorized actions.
The company identified a specific attack pattern: a POST request to `/api/session/reset_password` returning a 400 status code, immediately followed by a GET request to `/api/user/current` with a 200 status code. Organizations observing this pattern in their application or Metabase server ingress logs should assume their instance has been compromised. For those unable to upgrade immediately, Metabase advised temporarily blocking access to the `/api/session/reset_password` endpoint.
