Breaking: Metabase Zero-Day (CVSS 10.0) Under Active Exploitation — Multiple Victims Confirmed — 13 August 2026

Metabase Zero-Day Under Active Exploitation — CVSS 10.0, Multiple Victims Confirmed

A critical unauthenticated SQL injection vulnerability in Metabase is being exploited in the wild, with confirmed breaches of at least five organisations including Framework, n8n, and Kilo Code. Tracked as CVE-2026-72898, the flaw carries a CVSS v3.1 score of 10.0 and was added to CISA's Known Exploited Vulnerabilities catalog on August 11 with a remediation deadline of August 14.

The vulnerability exists in Metabase's password reset endpoint (`POST /api/session/reset_password`). An attacker needs no credentials and no user interaction. By sending crafted requests containing undeclared fields, the injection reaches the application database as structured input rather than a validated identifier, allowing arbitrary SQL execution against the Metabase application database. From there, the attacker gains full administrator access and can extract stored credentials for every database Metabase connects to, change application configuration, read and export data, and pivot into downstream systems.

Metabase confirmed the zero-day was used against its own cloud platform. The company has patched all cloud instances and released fixes for self-hosted deployments. Wiz estimates roughly 2,500 Metabase instances are internet-accessible, representing 25% of the 13% of cloud environments running self-hosted deployments. The blast radius extends well beyond Metabase itself: because Metabase stores credentials for every connected database and data warehouse, each compromised instance is a springboard into an organisation's broader data infrastructure.

Confirmed victim impacts include Framework (customer names, login IPs, addresses, phone numbers, and emails accessed), n8n (136 customer records breached, including 5 containing bcrypt-hashed passwords), and Kilo Code (Slackbot access tokens exposed). Other victims have not yet been publicly identified.

Affected versions span branches 58 through 63. Patches are available in 0.58.24, 0.59.21, 0.60.17, 0.61.11, 0.62.9, and 0.63.5 (and later). Organisations unable to patch immediately should block the `/api/session/reset_password` endpoint at the reverse proxy. After patching, revoke all active sessions (clear the `core_session` table), rotate all connected database credentials, audit administrator accounts for unauthorised changes, and review query history and data warehouse logs for unauthorised access.

CISA's August 14 deadline for federal agencies means the window for patching is measured in hours, not days. For private sector organisations running self-hosted Metabase, the same urgency applies. An unauthenticated CVSS 10.0 with confirmed victims and active exploitation is a patch-now event, not a patch-next-Tuesday event.

Also added to CISA's KEV catalog on the same day: CVE-2026-20349, a CVSS 8.6 denial-of-service vulnerability in Cisco Secure Firewall ASA and FTD that is under active exploitation. An unauthenticated attacker can crash VPN appliances with a single crafted HTTP request. Cisco has released patches. If you run Cisco ASA/FTD with remote-access VPN services enabled, patch immediately. Additionally, CVE-2026-8037 (Progress LoadMaster, CVSS 9.6) was added to KEV on August 7 with confirmed exploitation involving 792 reported attack attempts. Unauthenticated command injection on load balancers is another patch-now priority.

So what / Action: Inventory every Metabase instance in your environment, including dev and staging. If it is self-hosted and unpatched, treat it as potentially compromised, not just vulnerable. Block the reset password endpoint at the perimeter now. Patch. Then rotate every credential Metabase had access to. For Cisco ASA/FTD: if remote-access VPN is enabled, patch to prevent DoS attacks that take down your remote workforce connectivity. For Progress LoadMaster: patch immediately if you have any internet-facing instances. Three KEV additions in one week with active exploitation across all three is a clear signal that the window between disclosure and weaponisation has closed to near-zero.