CVE-2026-72898, CVSS 10.0, lets a remote, unauthenticated attacker inject arbitrary SQL through Metabase's own /reset_password endpoint and walk away with administrator access to the connected instance. CISA added it to the Known Exploited Vulnerabilities catalogue on 11 August 2026, one day after NVD published it.
The password-reset flow is the attack surface
Metabase is a business intelligence tool — the layer many organisations put in front of their production databases specifically so analysts and executives can query data without needing raw database credentials. That framing matters here because of exactly which endpoint carries this vulnerability: not a query builder, not a dashboard-rendering path, but the password-reset flow, a feature that by necessity must be reachable by someone who isn't yet authenticated, because the entire point of a password reset is helping a locked-out user regain access.
An unauthenticated SQL injection in that specific flow means the vulnerability sits precisely where an application cannot simply require prior authentication to close it — the feature's purpose is incompatible with that fix. The result, per NVD, is not merely data exposure but full administrator access to the Metabase instance, which for a BI tool means read access to every data source it's connected to and the ability to reconfigure what those connections do.
Why a one-day gap to KEV should change how you read every future BI-tool CVE
Business intelligence and analytics platforms have historically received less dedicated security review than the production databases they query, on the reasoning that they are a read-only convenience layer sitting downstream of the systems that actually matter. CVE-2026-72898 is a direct rebuttal to that reasoning: administrator access to a BI tool is administrator access to every connection it holds, which in most deployments includes credentials or connection strings to one or more production data sources.
Why "read-only convenience layer" is the wrong mental model
Organisations frequently deploy BI tools specifically so that people who shouldn't hold direct database credentials — analysts, product managers, executives — can still query production data through a controlled interface. That framing quietly implies the BI layer itself is lower-stakes than the database behind it, since it's "just" a query interface. CVE-2026-72898 breaks that assumption cleanly: the compromise doesn't require attacking the production database directly at all. It requires attacking the convenience layer sitting in front of it, which by design already holds the credentials needed to reach that data — meaning the BI tool's own security posture is not a secondary concern relative to the database's, it's an equally direct path to the same data.
What to check this week
Patch immediately — a one-day disclosure-to-KEV gap on a CVSS 10.0 unauthenticated SQL injection leaves no room for a normal review cycle.
Audit what data sources your Metabase instance is connected to, and what privilege level those connections use. If exploitation occurred, the practical damage ceiling is defined by what the compromised instance could reach, not by Metabase's own data.
Review whether the /reset_password endpoint, or Metabase generally, is reachable from outside your organisation's network. Restricting BI tooling to internal access only removes the unauthenticated precondition this specific CVE depends on.
Rotate credentials for any data source connection configured in Metabase, treating this the same as any other admin-access compromise — patching stops new exploitation, it does not undo what an existing session or exported credential already accomplished.
Why authentication-adjacent endpoints deserve extra scrutiny generally
Password-reset flows, account-recovery mechanisms, and similar authentication-adjacent features are a recurring source of serious vulnerabilities across many products precisely because they must, by design, be reachable without a prior valid session — the exact property that makes ordinary authentication requirements insufficient as a defence for that specific code path. Any security review of a self-hosted application should treat these flows as a distinct, higher-scrutiny category rather than assuming the same general hardening applied elsewhere in the application covers them equally.
How Safeguard helps
Safeguard's continuous inventory extends to analytics and business-intelligence platforms, tracking them with the same rigor applied to the production databases they connect to — closing the gap that treats BI tooling as a lower-risk convenience layer when, as this CVE demonstrates, it frequently holds the keys to everything behind it.
