Critical SQL Injection Flaw Exposes Metabase Users to Data Breach Risks

Metabase, a widely used business intelligence platform, has uncovered a severe zero-day SQL injection vulnerability that threatens the security of customer data, including sensitive credentials, tokens, and API keys. This flaw, designated as CVE-2026-72898, received a critical severity score of 10, the highest possible ranking, with affected versions starting from 1.58.

As David Shipley, CEO of Beauceron Security, points out, such a high CVSS score is rare and indicative of a significant risk. SQL injection vulnerabilities, while not new, remain dangerous as demonstrated by active exploitation efforts. There’s already proof of concept code circulating that malicious actors can utilize for attacks.

Unrestricted Database Access

Metabase's platform allows integration with prominent databases such as Databricks, MongoDB, Oracle, Snowflake, Amazon, and BigQuery for analytics, data visualization, and dashboard creation. However, the security breach allows attackers to gain "unmitigated, raw" access to the underlying database, affecting any data connected through Metabase.

A recent analysis by Wiz revealed that around 2,500 Metabase instances are on the internet, with roughly 25% of self-hosted versions publicly accessible. The vulnerability enables attackers to exploit the /api/session/reset_password endpoint to gain unauthorized access.

Upon identifying the vulnerability, Metabase acted quickly to block the exploited endpoints, apply patches, and invalidate affected sessions. While users of Metabase Cloud have been secured with immediate updates, self-hosted deployments need users to ensure they are patched to avoid being compromised.

Scott Miserendino, CTO at DataBee, elaborated on the risk, stating, “This vulnerability permits attackers to execute raw SQL commands on the Metabase database.” This access could lead to the theft or alteration of credentials, unauthorized admin account creation, changes to app configurations, and even the potential degradation of vital information.

Furthermore, users of OEM versions of Metabase might remain unaware of their exposure since the product is integrated into third-party offerings. Miserendino emphasizes the seriousness of this vulnerability and the potential for widespread repercussions.

Impacted Organizations

The breach appears to have primarily affected small businesses and startups, including Kilo Code, recently acquired by Anaconda; Y Combinator-backed Tally, developing autonomous accounting solutions; personal computer manufacturer Framework; automation platform n8n; and API testing provider ChecklyHQ.

Reports indicate that these firms faced potential breaches involving usernames, email addresses, cloud passwords, and cryptographic tokens. Following the attack, they have initiated direct communication with affected customers, implementing measures such as credential rotation, password resets, and reviewing internal audit logs.

Checkly acknowledged the issue, stating, “While the vulnerability was in a vendor product, safeguarding our data is our responsibility.” They’re revisiting their processes to enhance data sanitation and management during analytics operations.

Response and Recommendations for Customers

According to Metabase, the attack exhibited the following pattern:

• A call to POST /api/session/reset_password triggers a 400 status code.
• This is followed by a successful call to GET /api/user/current with a 200 status code.

Customers should review their application logs for this activity, as it may indicate that their Metabase instance has been compromised. Immediate updates to appropriate patches are crucial; for example, those running version 0.58.6 should upgrade to at least 0.58.24. If an upgrade isn't feasible, blocking the /api/session/reset_password endpoint temporarily might help mitigate risks.

To bolster security, organizations should revoke all active user sessions if the aforementioned endpoint is publicly accessible, audit API keys and logs for unauthorized access, and rotate credentials for all linked databases.

Miserendino additionally recommends that enterprises performing custom SQL integrations implement their own SQL injection detection through a web access firewall (WAF) or reverse proxy. Continuous monitoring of security logs for new administrator accounts or unusual data activity is essential.

Finally, Anaconda has urged its customers to remain vigilant against potential phishing attempts and to maintain strict credential hygiene by regularly auditing, reviewing, and rotating credentials.