On August 6, 2026, Metabase disclosed active exploitation of a zero-day vulnerability affecting Metabase Cloud and self-hosted Metabase installations running affected releases in the 58 through 63 branches. The vulnerability allows an unauthenticated remote actor to inject SQL commands into the Metabase application database and potentially obtain administrative access to the Metabase instance.
The technical impact extends beyond compromise of the Metabase application database. Metabase stores configuration required to connect to external databases and data warehouses. According to the vendor advisory, an attacker who obtains administrative access can modify application configuration, retrieve stored database credentials, query data available through connected data sources, and export that data.
View the full Metabase incident report in VenariX
Framework, n8n, Kilo Code, and Tally have confirmed security incidents associated with affected Metabase environments. The incidents are separate breaches at separate organizations, but they share the same underlying technology exposure.
Metabase Vulnerability Details
GitHub Security Advisory GHSA-vwf4-m7j8-wcjf describes the issue as a critical, CVSS 10 SQL injection vulnerability in Metabase’s password-reset functionality. The flaw requires no authentication or user interaction and can be exploited remotely against exposed instances.
On August 11, 2026, the Cybersecurity & Infrastructure Security Agency (CISA) assigned CVE-2026-72898 to the Metabase SQL injection vulnerability with a CVSS score of 10.
Exploitation Path and Database Access
The vulnerability affects the /api/session/reset_password endpoint and allows SQL injection into the Metabase application database. Successful exploitation can lead to administrative access to the Metabase instance, including access to configured database connections and their stored credentials.
Because Metabase is commonly connected to external databases and data warehouses, a compromise of the application can extend to those underlying data sources. The extent of that exposure depends on how the environment was configured. A deployment connected only to a restricted reporting database presents a substantially different risk from one connected to a production warehouse containing customer, account, or operational data.
For affected organizations, the investigation should establish which data sources were connected to Metabase, what privileges those credentials had, and whether database or query logs show unauthorized access. Metabase specifically recommends rotating connected-database credentials and reviewing warehouse logs after a suspected compromise.
Confirmed Downstream Incidents
Multiple organizations have confirmed data exposure associated with compromised Metabase Cloud environments. The scope of each incident depends on the data and permissions available through the affected deployment.
The Metabase vulnerability has already been tied to fifteen publicly confirmed incidents:
The scope of each breach depends on the data sources and permissions configured in the affected Metabase environment.
Dire Wolf Activity
VenariX has confirmed that Dire Wolf, a ransomware and data extortion threat actor, exploited CVE-2026-72898 in at least two incidents involving self-hosted Metabase deployments:
VenariX suspects the group may have targeted fourteen additional companies in this manner. There is currently no evidence that the threat actor discovered the zero-day or is behind the other confirmed Metabase-related incidents.
Detection
Metabase identified a recurring HTTP pattern associated with exploitation:
POST /api/session/reset_passwordreturning HTTP400Followed by
GET /api/user/currentreturning HTTP200
Metabase states that this pattern in application or ingress logs indicates that the instance was likely compromised.
Organizations investigating an affected deployment should also review Metabase query history, database and warehouse audit logs, administrator accounts, API keys, and unexpected use of stored database credentials.
Remediation
Metabase patched its Cloud environment and released fixed versions for affected self-hosted branches. Customers should upgrade to the latest patched release available for their version. If an immediate upgrade is not possible, Metabase recommends temporarily blocking access to /api/session/reset_password.
For potentially exposed instances, Metabase also recommends:
Revoking active sessions
Reviewing administrator accounts and API keys
Rotating credentials for connected databases
Reviewing Metabase and warehouse logs for unauthorized activity.
Credential rotation is especially important if exploitation is suspected, because patching the application does not invalidate credentials that may already have been exposed.
Track Metabase Exposure in VenariX
VenariX allows users to track downstream exposure tied to specific technologies. For the Metabase incident, users can filter incidents by Platforms & Tools and search for Metabase Cloud to identify organizations with confirmed exposure linked to the vulnerability.
Framework, n8n, Tally, and Kilo Code appear as separate incidents, allowing each breach to retain its own affected data, scope, and impact while remaining searchable through the common Metabase technology.
As additional organizations disclose Metabase-related incidents, they can be identified through the same filter.
Track Metabase-related incidents in VenariX using the Platforms & Tools filter.
