Exploitation reportedFri, 6 Nov 2026
Metabase exploitation: block the vulnerable endpoint, update and review database access
An unauthenticated SQL-injection vulnerability in Metabase has been exploited and may expose administrative access and database credentials. Update immediately, temporarily block the password-reset endpoint, revoke sessions and investigate data access.
Article
Metabase confirms exploitation of CVE-2026-72898, rated CVSS v3.1 10.0. An unauthenticated attacker who can reach an affected self-hosted instance may use SQL injection to gain Metabase administrative access, obtain stored database credentials, and query or export data readable by connected accounts.
- 01
Unauthenticated endpoint reachable
The attacker can connect to affected self-hosted Metabase
- 02
SQL injection in the application database
A malicious request affects Metabase's own application database
- 03
Platform administrative access obtained
Settings may be changed or stored database credentials read
- 04
Data queried and exported
The impact depends on the connected account's readable data and permissions
Patched versions and required post-upgrade actions
The vendor currently recommends updating the applicable branch to x.58.24, x.59.21, x.60.17, x.61.11, x.62.9, x.63.5 or a later patched release in that branch. Here, x is 0 for the open-source edition or 1 for the commercial edition. Verify actual versions for every container image and outsourced instance.
Official affected-version boundaries differ. The GHSA lists earlier branch upper limits than its Patched versions field, while the CVE record and CSA use the later recommended patched versions as the boundary. Use the vendor's current recommended update targets above rather than deciding that a system is safe solely from an earlier boundary.
If an immediate update is not possible, the vendor recommends temporarily blocking /api/session/reset_password. If this endpoint was publicly reachable, follow the vendor's post-upgrade instructions to revoke sessions, review keys and administrators, rotate credentials for all connected databases, and examine data-warehouse records and Metabase activity and query history.
- 01
Block the endpoint and update
Inventory self-hosted, outsourced and container instances. If an immediate upgrade is not possible, block /api/session/reset_password at the actual entry points, then update the applicable branch and retest every entry point.
See what to doResources: 2
TWISA member solutions
Block the endpoint and update
Inventory self-hosted, outsourced and container instances. If an immediate upgrade is not possible, block /api/session/reset_password at the actual entry points, then update the applicable branch and retest every entry point.
- 02
Revoke sessions and review identities
If the endpoint was publicly exposed, administrators should follow the vendor's instructions after upgrading to empty core_session in the application database and revoke all sessions. Review API keys and administrator changes.
See what to doResources: 2
TWISA member solutions
Revoke sessions and review identities
If the endpoint was publicly exposed, administrators should follow the vendor's instructions after upgrading to empty core_session in the application database and revoke all sessions. Review API keys and administrator changes.
- 03
Rotate database credentials
Rotate credentials for connected databases, verify application connections, restrict query and export permissions, and inventory readable sensitive data and authorization to decrypt plaintext.
See what to doResources: 2
TWISA member solutions
Rotate database credentials
Rotate credentials for connected databases, verify application connections, restrict query and export permissions, and inventory readable sensitive data and authorization to decrypt plaintext.
- 04
Investigate access and recover
Review data-warehouse, reverse-proxy and application records, activity and query history. If anomalies are found, preserve evidence, isolate and recover from trusted sources, and verify reports and data integrity.
See what to doResources: 2
TWISA member solutions
Investigate access and recover
Review data-warehouse, reverse-proxy and application records, activity and query history. If anomalies are found, preserve evidence, isolate and recover from trusted sources, and verify reports and data integrity.
Inventory entry points, open-source or commercial editions, container images, connection accounts and sensitive data
Allow authorized traffic and apply controls at each layer.
- 01
Public and internal entry points
Reverse proxies and the vulnerable endpoint
Block and retestTemporarily block the password-reset endpoint, restrict sources and prevent direct-access bypasses
- 02
Analytics platform
Metabase and its application database
Update and review accessUpdate the applicable branch, revoke sessions, and review API keys and administrators
- 03
Databases and data warehouses
Service credentials, queries and exports
Reduce the scope of data exposureRotate credentials, apply least privilege, and separate sensitive plaintext from decryption authorization
Feed logs and traffic data from each layer into monitoring and response.
- Monitoring and recoveryCorrelate application, proxy and data-warehouse records. Investigate unusual administration, queries and exports, preserve evidence and verify trusted backups.
Proactive testing and retesting
With authorization, perform asset discovery, vulnerability scanning, penetration testing, API testing and attack simulation. Verify endpoint blocking, patched versions and data permissions at every entry point. For WAF or proxy rules, compare requests, alerts, actual blocking and backend results, and check direct paths that bypass the proxy. Retest after changes. Separate decryption authorization from data encryption and masking; disk encryption cannot limit a compromised account that already has legitimate query rights.
TWISA member solutions
Supporting: Block the endpoint and update
Applicable offer: SkyCloud's cybersecurity protection package can support traffic and WAF protection planning at public website entry points. First-time adopters must obtain assessment reports before and after implementation, then submit the reports to apply for a TWISA-exclusive discount code by 2026/12/31. The offer uses targeted invitations and review. Verify password-reset endpoint blocking against the actual reverse proxies and rules at every entry point.
Inventory self-hosted, outsourced and container instances. If an immediate upgrade is not possible, block /api/session/reset_password at the actual entry points, then update the applicable branch and retest every entry point.
Supporting: Revoke sessions and review identities
If the endpoint was publicly exposed, administrators should follow the vendor's instructions after upgrading to empty core_session in the application database and revoke all sessions. Review API keys and administrator changes.
Supporting: Rotate database credentials
Rotate credentials for connected databases, verify application connections, restrict query and export permissions, and inventory readable sensitive data and authorization to decrypt plaintext.
Supporting: Investigate access and recover
Review data-warehouse, reverse-proxy and application records, activity and query history. If anomalies are found, preserve evidence, isolate and recover from trusted sources, and verify reports and data integrity.
Official sources
- Metabase: SQL injection, patches and post-upgrade guidance
- Cyber Security Agency of Singapore: exploitation and temporary mitigation
- CVE Program：CVE-2026-72898
Contact the relevant members for more detailed product and service information.
Advisory updated: 2026/11/06. Consult the vendor's latest information for product support and patch status.