Framework Leaks Every Customer via Metabase Zero Day

On 6 August 2026 at 8:26pm Pacific, Framework emailed its customers to say their contact details had been taken. Not from Framework's servers. From a dashboard tool most of those customers had never heard of, sitting one hop upstream of the company they actually bought a laptop from.

Key Takeaways

• Framework disclosed on 6 August 2026 that attackers accessed customer full names, email addresses, login IP addresses, phone numbers and billing and shipping addresses through a compromise at Metabase, its business intelligence vendor.
• The root cause is CVE-2026-72898, an unauthenticated SQL injection in Metabase scoring a CVSS base score of 10.0, which CISA added to its Known Exploited Vulnerabilities catalog on 11 August 2026.
• Framework spokesperson Eric Schumacher confirmed the incident touched "all customers" but declined to give a number. No payment information or order records were accessed.
• The same zero day also hit Tally, Kilo Code and n8n, and n8n reported only 136 affected records against Framework's entire customer base, a difference driven by how much personal data each company had loaded into the tool.
• Because no password was stolen, there is no credential to rotate, and the exposed name plus email plus purchase relationship stays useful to phishing crews indefinitely.

What Exactly Did Framework Disclose?

Framework told customers that an attacker reached the company's Metabase Cloud instance and read the customer table inside it. The notification lists full name, email address, login IPs, and billing and shipping address information including country, city, state, zip code, phone number and company. Business customers may additionally have had VAT and EIN details exposed. Framework stated that no other personally identifiable information, order information, or payment information was accessed.

The timeline is unusually tight. Metabase detected the attack on 3 August 2026 and notified Framework at 9am Pacific on 6 August. Framework's customer email went out the same evening. TechCrunch reported that spokesperson Eric Schumacher confirmed the breach affected "all customers" while declining to give a count, though Framework has sold hundreds of thousands of devices since 2021.

Framework says it rotated credentials on every database connected to its Metabase instance, found no changes to admin accounts, saw no evidence of access to systems outside Metabase, and has engaged an outside forensic firm.

What Is CVE-2026-72898?

CVE-2026-72898 is an unauthenticated SQL injection flaw in Metabase that lets a remote attacker with no credentials gain administrator access to a Metabase instance. NIST's National Vulnerability Database rates it 10.0 on both CVSS 3.1 and CVSS 4.0, the maximum possible score.

The bug lives in the publicly reachable POST /api/session/reset_password endpoint and affects every release from 1.58 onward. Security firm Wiz's teardown of the exploit chain describes a sequence of individually reasonable decisions that combine badly: a Clojure merge that preserves attacker supplied keys when authentication fails, JSON keywordization that turns a payload like {"user-id": {"raw": "SQL"}} into a Clojure map, and HoneySQL's :raw directive, which by design bypasses parameterization. The query expects an integer user id and instead receives an instruction.

Once an attacker holds Metabase admin, they inherit everything Metabase can reach. Help Net Security reported Metabase's own assessment: attackers could steal stored credentials for connected databases, read anything reachable through those connections, and export it. A typical BI deployment holds live connection strings for Snowflake, BigQuery, Redshift, Postgres and MongoDB. Admin on the dashboard is admin on the warehouse.

CISA added the flaw to its KEV catalog on 11 August 2026 with a remediation deadline of 14 August, three days, which is about as loud as CISA gets.

Why "Only Contact Data" Understates the Risk

No password was stolen, and that is the problem, not the consolation. A leaked password hash creates a task with an end state: reset it, and the stolen artifact is worthless. Framework customers have no equivalent action available. Their name, email, phone number and shipping address are now correct, verified, and permanently correlated with a confirmed purchase from a specific company.

That combination is the expensive part of a phishing campaign, and the attackers got it for free. The same dynamic played out in the Alcon breach that leaked 218,000 business email addresses. The record itself looks harmless in a summary and is worth real money in a list.

Login IPs add a second layer. They are approximate location and connection history, useful for making a fraudulent message look contextually plausible.

Why Framework's Customer List Is Worth More Than Average

Framework sells a laptop you are expected to open with a screwdriver. The buyers skew hard toward engineers, sysadmins, Linux users and open source contributors, people who self select into a product because they want firmware control and part level repairability.

For an attacker running a targeted campaign, that demographic is not a retail list. It is a list of people who plausibly hold GitHub credentials, cloud console access, package registry publishing rights, CI secrets and production SSH keys. A single successful compromise against a maintainer can reach far past that person's own accounts, which is why a supply chain oriented crew would pay more for 10,000 Framework buyers than for 500,000 generic ecommerce customers. Expected value per address, not volume, is what makes this list dangerous.

What This Means for Your Inbox

Every affected customer should expect Framework branded email that is not from Framework. The attackers know your name, know you bought hardware, know where it shipped, and in many cases know roughly where you connect from. That is enough to write a message that survives the two second scan most people give an inbox.

Treat any unexpected Framework email as untrusted regardless of how well it reads. Do not click order links. Open framework.com directly and check the order status inside your account. Be especially wary of messages referencing the breach itself, since "we are contacting affected customers" is now a perfectly credible pretext for anyone who has the list. Watch for shipping and customs variants too, which map neatly onto the address data that leaked.

Move the account to phishing resistant multi factor authentication. CISA's guidance on phishing resistant MFA is explicit that SMS codes can be relayed by an attacker in real time, while passkeys and FIDO2 hardware keys are bound to the origin and cannot be replayed against a lookalike domain. If you use a per vendor alias or plus addressing, keep doing it. The address that starts receiving fraud tells you exactly which vendor leaked, and you can burn it without touching your primary mailbox.

The Breach Moved One Hop Upstream

The structural story of 2026 is that customer data keeps escaping through companies the customer never chose. Trezor's buyers lost names, addresses and phone numbers through a compromise at fulfilment provider ShipMonk that affected 13,689 customers. Steam hardware buyers were exposed through the CEVA Logistics intrusion, which also reached Bol, De Bijenkorf and ING. Amgen's patient data leaked through third party cloud environments. Framework now joins the list, and the Privacy Guides roundup for 7 to 13 August had to cover four such incidents in one week.

Here is the comparison the coverage has not made. Four companies were hit through the same Metabase flaw on the same day by the same attacker. n8n published a forensic breakdown accounting for 136 records: 7 with usernames and emails, 5 with bcrypt hashed passwords, the rest partial or empty. Framework notified everyone it has ever sold to. Tally lost emails and password hashes. Kilo Code lost Slack access tokens.

Identical vulnerability. Blast radii separated by several orders of magnitude. The variable was not attacker skill or security spend, it was how much personal data each company had chosen to pipe into an analytics tool. Framework's own remediation note concedes the point: the company says it is now evaluating the breadth and depth of data shared with business intelligence platforms and scoping access down to only the columns required for analysis.

For a shopper, this means personal risk is now a function of a vendor list you cannot see and cannot enumerate. Nobody buying a laptop consented to Metabase, and no amount of consumer diligence would have surfaced it before 6 August.

What Engineering Teams Should Take From This

The uncomfortable question for anyone running a data stack is why a BI warehouse holds a customer's phone number and street address at all. Analytics answers questions about cohorts, conversion and geography. Almost none of those queries need an identity. A hashed or tokenized customer key plus a city and a country field satisfies the dashboard while making the export worthless. Framework's postmortem commitment to column level scoping is the correct fix, and it costs nothing to implement before an incident rather than after one.

Three practical controls follow. Inventory which of your vendors hold direct PII rather than pseudonymous identifiers, and treat every one as a breach you will eventually have to disclose under your own brand. Confirm through your DPA and contract terms, not a trust page, who is obligated to notify you and how fast; Metabase reached Framework in three days, which is genuinely good and should be the contractual floor. Finally, audit internet exposure of self hosted BI instances, because a dashboard reachable from the public internet with live warehouse credentials inside it is a single CVE away from being your worst day.