decrypted · 8 august 2026 · vulnerabilities and patching · supply chain · uk policy and law

The Metabase flaw in a password reset box, and the customers it caught

A single unauthenticated web page in the open-source analytics tool Metabase let attackers write their own instructions into a customer's database and walk out the other side as an administrator. Metabase rates the flaw the maximum 10.0 on the CVSS scale, says it was under active exploitation before any fix existed, and this week two of its customers, the laptop maker Framework and the form-builder Tally, confirmed their Metabase instances were breached as a result. For any UK organisation that has plugged a BI or dashboard tool into a production database, this is a live warning rather than an abstract one.

How a password reset became a database break-in

The vulnerable code sat behind the page for resetting a forgotten password, reachable by design without logging in first. The flaw is that Metabase took part of what a visitor submitted there and dropped it straight into a database query instead of treating it purely as data. Picture a hotel where guests fill in a slip to request a password reset, and the porter reads the slip aloud into a microphone wired to the safe's lock: phrase the slip correctly and the porter, meaning only to help, opens the safe instead. That is SQL injection, a class of bug that has been well understood and avoidable for decades through basic coding hygiene. Metabase's own advisory, tracked as GHSA-vwf4-m7j8-wcjf since no CVE has yet been assigned, confirms active exploitation. Framework told customers that attackers accessed its instance on 3 August and obtained names, email addresses, phone numbers and physical addresses; Tally reported its own environment compromised the same day. Metabase has shipped fixes across every supported release line and says Cloud customers were patched automatically; anyone self-hosting version 1.58 or later needs to upgrade without delay and treat the reset-password endpoint as compromised if it was internet-facing.

The Secure by Design lesson

The coding mistake is specific, but the blast radius is the generic lesson. Metabase instances typically hold live credentials for a company's actual production databases, so admin access to Metabase meant read access to whatever it was connected to. That is a recurring failure in analytics and reporting tooling: a convenience layer sitting in front of sensitive data, reachable before login, carrying credentials scoped far wider than the reporting job needs. UK organisations running any self-hosted BI, monitoring or reporting tool should ask two questions this week: does it expose anything reachable before authentication, and does its database credential have write access, or access to tables it never actually queries. Tighter scoping on that connection would not have stopped the SQL injection, but it would have shrunk what an attacker could do once inside.

Also this week

A supply-chain attack hit the npm ecosystem on 4 August after the maintainer account behind the widely used keyv and cacheable package families was compromised. The attacker republished at least ten packages directly, and through the ordinary chain of one package depending on another, the malicious code spread into several hundred downstream packages collectively pulling tens of millions of weekly downloads. The payload harvested AWS, GCP, Azure, GitHub and npm credentials and republished itself into any further package the stolen tokens could reach; researchers at Socket and Chainguard tie it to the same Shai-Hulud malware lineage seen earlier this year. Most affected teams never installed keyv directly: it arrived as a dependency of a dependency. Any UK engineering team running a dependency audit this week should check transitive dependencies specifically, not just the packages named in package.json.

The ICO told the government on 30 July that it has reached a genuine legal ceiling on how far it can let companies test AI products against real people's data. Its existing regulatory sandbox can grant limited flexibility, but a full statutory sandbox, one letting firms test against live personal data in ways that push against data protection principles, needs primary legislation that only Parliament can pass. The ICO says such a scheme is feasible in principle and will speed up its current sandbox in the meantime, with legal services named as an early candidate area. It amounts to a regulator saying it could offer more room to manoeuvre but will not do so without a democratic mandate, worth remembering next time a vendor argues that regulation alone is holding back British AI.

Sources

Questions about scoping BI or analytics tool access to your production data? get in touch.

More like this

Get the next post by email: subscribe to Decrypted. Double opt-in, unsubscribe any time, or take the RSS feed.

Prefer to listen? Decrypted on Apple Podcasts, or paste the podcast feed into any app.