Metabase is the quiet tool in a client’s stack. It draws the charts. Nobody threat-models the chart tool. But to draw the charts it holds standing credentials to the data warehouse, the production replica, the billing database — whatever anyone ever connected. Wednesday, Metabase disclosed that its own cloud platform was attacked through a previously unknown vulnerability, that a fix is out, and that self-hosted instances are still exposed until someone upgrades them. That someone is your clients.
The flaw is an unauthenticated S Q L injection reachable through the password-reset endpoint. No login required. Metabase’s advisory rates it C V S S 10.0 — the top of the scale — and confirms active exploitation. It has no C V E number yet. Do not wait for one.
From there, the attacker could change the application configuration, steal stored credentials for the connected databases, read any data accessible through those connections, and export data. Metabase has confirmed active exploitation of this vulnerability.
Look at that fingerprint again, because it is the detail I’d lead every client call with. The injection rides a request that returns an error. Four hundred. The kind of line log pipelines drop to save storage, the kind dashboards grey out. The attacker’s failure code is the attack; the tidy 200 that follows is them walking through the door. Whole monitoring philosophies assume errors are noise. This one is the signal.
It is already biting named companies. Framework — the laptop maker — told all its customers that names, emails, phone numbers and physical addresses were taken through its Metabase instance; per its notice, the attacker was in on August 3 and Metabase surfaced it on August 6. Three days from access to disclosure. The accounting platform Tally disclosed the same week.
The order of operations, per Metabase’s own guidance. Upgrade or block — every self-hosted instance to its minimum safe release; where that can’t happen today, block the reset-password endpoint at the proxy. Hunt the fingerprint — grep application and ingress logs for the 400-then-200 pair. If the endpoint was public, assume the worst after upgrading: delete every row in core_session, review A P I keys and admin accounts, rotate credentials on every connected database, and read the warehouse logs — the blast radius is what Metabase could see, not Metabase itself.
Kept honest. No C V E exists yet, so vulnerability scanners keyed to C V E feeds may report clean instances that are exposed — version numbers are the test, not scan results. The advisory’s affected-version ranges and the blog’s minimum-safe list disagree at the edges (the advisory implies 63.3 closes it; the blog says 0.63.5 is the floor) — I’d follow the blog’s higher numbers and lose nothing. The Framework and Tally details come from their notifications to customers as reported consistently by two independent outlets, not from a page I could fetch — the vulnerability facts all come from Metabase’s own advisory and blog.
Sources, fetched today, August 8, 2026. (1) Metabase security advisory GHSA-vwf4-m7j8-wcjf, SQL injection using an unauthenticated endpoint leading to admin access, published August 6, 2026, github.com/metabase/metabase/security/advisories — source of the severity (Critical), affected and patched version ranges, the quoted blast-radius sentence, and the confirmation of active exploitation. (2) Metabase, Security incident update, metabase.com/blog/security-update, fetched today — source of the cloud-attack disclosure, the minimum-safe-release list (0.58.24 / 0.59.21 / 0.60.17 / 0.61.11 / 0.62.9 / 0.63.5), the below-58-not-vulnerable line, the 400-then-200 attack pattern, the endpoint-blocking workaround, and the post-upgrade checklist (core_session, A P I keys, admin review, credential rotation, warehouse logs). (3) Framework and Tally: their disclosures to customers, cross-checked across two independent reports — TechCrunch (August 7, quoting Framework’s notice and spokesperson) and BleepingComputer (August 7) — which agree on the data categories, the August 3 access date and the August 6 notification; no vulnerability fact in this edition rests on either outlet.
Metabase — the BI tool half your clients run against their production data — disclosed a zero-day Wednesday. It deserves more attention than it's getting. The shape of it: — Unauthenticated SQL injection through the password-reset endpoint. No login needed. — Metabase rates it CVSS 10.0. There is no CVE number yet. — Active exploitation is confirmed — this was found because Metabase's own cloud was attacked. — End state: admin access, then the stored credentials for every database the instance connects to. In Metabase's own words: "read any data accessible through those connections, and export data." Cloud instances are already patched. Self-hosted instances are exposed until someone upgrades them. Below version 58 isn't affected. Minimum safe releases: 0.58.24 / 0.59.21 / 0.60.17 / 0.61.11 / 0.62.9 / 0.63.5. Here's the detail I'd lead every client conversation with. The attack's log fingerprint is: POST /api/session/reset_password → 400 GET /api/user/current → 200 The break-in *is* the failed request. A 400 — the exact kind of line log pipelines drop and dashboards grey out. If your monitoring treats errors as noise, the only trace you kept is the attacker's success. That's worth an incident-review conversation entirely on its own. It's already biting named companies: Framework told all its customers that names, emails, phones and addresses went out through its Metabase instance — attacker in on August 3, notified August 6. Tally disclosed the same week. The weekend list, straight from Metabase's guidance: 1. Upgrade every self-hosted instance to its minimum safe release. Can't today? Block /api/session/reset_password at the proxy. 2. Grep application and ingress logs for the 400-then-200 pair. 3. If the endpoint was public: after upgrading, clear all sessions (core_session), review API keys and admins, rotate every connected database credential, and read the warehouse logs. One trap: no CVE means CVE-keyed scanners will call vulnerable instances clean. Check versions, not scan results. Advisory GHSA-vwf4-m7j8-wcjf, August 6. The quiet tool is the loud risk.
Use the MRP Personal Design System (Signature). Create a 1080x1350 animated piece titled "A 400, Then a 200." Bone field (#F4F1EC), Ink type (#141414), Coral Deep (#D9401F) for kicker, labels and rules; Coral Bright (#FF6A4D) spent EXACTLY TWICE — once on "200" when the second log line lands in beat 3, once on the final line of the end card. Cormorant for the big figures and end card; Manrope Light for captions, log lines and footer; Italiana for the SignatureMark. Tall, airy, left-aligned. Max 3 type moves. The piece is TWO LINES FROM A LOG FILE, READ SLOWLY. No terminals drawn, no skulls, no padlocks, no matrix rain. Typography only. Sequence (about 40 seconds): 1. (0-5s) Kicker top-left, letter-spaced uppercase Manrope in Coral Deep, types on: "METABASE · GHSA-vwf4-m7j8-wcjf · CVSS 10.0 · ACTIVELY EXPLOITED". Below, one Manrope Light Ink line fades up: "the quiet tool holds the keys to everything it graphs." Hold. 2. (5-14s) A large Cormorant Ink figure lands upper-left: "10.0" with Manrope Light caption "the top of the severity scale. no CVE yet." Hold, then dim to pale Ink and hold place. 3. (14-26s) Two log lines set in Manrope, generous spacing, one after the other. First: "POST /api/session/reset_password — 400" in Ink with a small Coral Deep rule before it; caption beneath fades up: "the break-in. it logs as a failure." Beat. Second line: "GET /api/user/current — 200" — the "200" warms to Coral Bright (moment 1 of 2); caption: "the attacker, inside." HOLD both lines, unvoiced, at least two seconds. 4. (26-33s) The log lines dim but stay. Three short Manrope Light lines fade in below, each with a small Coral Deep rule: "upgrade to the minimum safe release" / "or block the endpoint at the proxy" / "then hunt this pair in your logs". 5. (33-40s) Clear. End card in Cormorant, three lines, the third warming to Coral Bright (moment 2 of 2): "Errors aren't noise." / "This one is the whole attack." / "Patch, then read your logs backwards." Footer in Manrope Light Ink: "METABASE ADVISORY GHSA-vwf4-m7j8-wcjf · AUG 6, 2026 · MIN SAFE: 0.58.24 / 0.59.21 / 0.60.17 / 0.61.11 / 0.62.9 / 0.63.5". SignatureMark bottom-left: Italiana "Meschelle Peterson" + code63labs. Motion language: fades and rules only; the two log lines must land with slow, deliberate timing — the piece's whole tension is the pause between the 400 and the 200. No bounce, no typewriter chatter after the kicker, no glitch effects. The design rests on beat 3 reading like evidence.
FIRST SOURCE · one verified original-source finding, composed for one reader · this edition: cybersecurity — written for the firms whose clients' quiet chart tool is wired to everything worth stealing