CVE-2026-72898 is a SQL injection vulnerability in Metabase Metabase. CISA added it to the Known Exploited Vulnerabilities catalogue on 11 August 2026, which means attackers have used it in real attacks. 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.
What this vulnerability means in Metabase
SQL injection in a business intelligence platform is dangerous because the attacker is not just querying data, they are reaching the layer that governs how the application talks to its databases. In a product like Metabase, that can turn a single injection flaw into broad read access and configuration tampering across connected data sources.
The key security concern is that the vulnerability sits at the boundary between the application and the databases it can reach. If an attacker can influence SQL execution, they may be able to pivot from one unsafe query into stored database credentials, application settings, and the data exposed through those connections.
Why this class of flaw is high impact
SQL injection remains one of the most consequential web application weaknesses because it breaks the trust boundary between user input and database execution. The OWASP Top 10 still treats injection-style flaws as a core application security risk for good reason: when input reaches a query engine unsafely, the attacker often inherits the application’s own access to data and commands.
For a platform that stores connection details and can reach multiple backend systems, the blast radius can be much larger than a typical single-table data leak. The attacker may not need direct database login if the application itself is already trusted to query, export, or manage those connections.
How organisations check exposure and verify scope
Exposure checks should start with asset inventory and version confirmation, then move to deployment review: where Metabase is running, whether it is internet-facing, and what databases it can reach. The CVE Program and the NIST National Vulnerability Database remain the authoritative references for record details, while the CISA KEV listing tells you whether exploitation has been observed in the wild.
In practice, the important question is not only “Is Metabase deployed?” but also “What databases, credentials, and exported datasets are reachable through that instance?” A vulnerability in a reporting tool becomes materially worse when it sits close to sensitive production data or has broad connector privileges.
Remediation, detection, and post-exploitation review
When patching cannot happen immediately, reduce blast radius by restricting network reach, tightening database permissions, and removing unnecessary connectivity paths. The Database Security Guide is a useful companion for understanding how application-to-database trust, service accounts, and auditing influence the impact of SQL injection.
Detection should focus on unusual query patterns, unexpected configuration changes, and suspicious export activity from the Metabase instance. After remediation, review whether database passwords, API tokens, session material, or related service credentials were exposed and rotate anything that may have been accessible through the compromised application.
Risk and Threat Considerations
Because this vulnerability is actively exploited and can expose both configuration and database access, the main risk is not limited to data theft, it is also operational compromise of a trusted analytics layer. Once an attacker can alter application settings or read stored secrets, they may persist, expand access, or exfiltrate data through legitimate-looking application paths.
Failure mechanism: SQL injection lets attacker-supplied input become executable database logic, which can reveal credentials, modify configuration, and widen access to connected systems.
Impact: Organisations can face data exposure, unauthorized exports, loss of trust in reporting outputs, and follow-on compromise of connected databases and dependent services.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP ASVS, CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V4 — API and Web Service | SQL injection is a core application input-to-query security failure. |
| V8 — Authorization | This flaw can bypass intended data-access boundaries through injected database actions. | |
| Recommendation — Validate server-side query handling and parameterisation in vulnerable application flows. Enforce authorization checks around every data-access path and privileged function. | ||
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | The issue depends on exposed, reachable application and database configurations. |
| CIS-5 — Account Management | Compromise may expose stored credentials and dependent service access. | |
| Recommendation — Harden deployed application and database configurations to reduce injection blast radius. Review and rotate accounts and credentials that the application can access. | ||
| NIST SP 800-53 Rev 5 | SA-11 — Developer Testing and Evaluation | SQL injection is a software flaw that testing and verification are meant to catch. |
| Recommendation — Test application inputs and database interactions for injection weaknesses before release. | ||
Practitioner Guidance
Why practitioners should care: Treat the Metabase instance as a high-value access broker, not just a dashboard. If it can reach sensitive databases, its security posture directly affects the confidentiality of those systems.
What to watch for: Review whether the application has excess database privileges, whether it is internet-exposed, and whether any stored credentials or connected data sources would need rotation if exploitation is suspected.
Practitioner takeaway: The right response is to pair vulnerability remediation with credential and access review, because SQL injection in a trusted data platform often creates identity and data impact beyond the initial flaw.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org