CVE-2026-59827 metabase vulnerability
Metabase is an open-source business intelligence and embedded analytics tool. Prior to 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4, Metabase instances with an H2 database connection, including the default sample database, deserialize arbitrary Java objects returned in H2 native query result columns of type OTHER without validation, allowing an authenticated user who can run native H2 queries to execute code on the Metabase server. This issue is fixed in versions 1.58.15, 1.59.12, 1.60.6.3, and 1.61.1.4.
Quick answer
metabase should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Metabase is affected by CVE-2026-59827, a unsafe deserialization and possible code execution risk. Metabase is an open-source business intelligence and embedded analytics tool. The recommended remediation is to update to Metabase 1.58.15, 1.59.12, 1.60.6.3, 1.61.1.4, or a later fixed release for the deployed branch. Until the update is complete, disable or tightly restrict native H2 query execution and remove default/sample H2 database exposure until patched, review logs, and reduce exposure of the affected service or workflow.
- Inventory every deployment, package, appliance, container, service, and managed environment that uses Metabase.
- Confirm the installed version and compare it with versions prior to 1 and the source advisory for CVE-2026-59827.
- Apply the vendor-supported fix: update to Metabase 1.58.15, 1.59.12, 1.60.6.3, 1.61.1.4, or a later fixed release for the deployed branch.
- If the update cannot be applied immediately, disable or tightly restrict native H2 query execution and remove default/sample H2 database exposure until patched; disable unnecessary public access, endpoints, integrations, uploads, management interfaces, or high-risk features until patched.
- Review application, device, reverse-proxy, WAF, package manager, container, authentication, and audit logs for activity related to CVE-2026-59827.
- Rotate sessions, API tokens, service credentials, integration keys, and administrator passwords if logs or affected data indicate compromise, code execution, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or appliances when appropriate, and remove temporary files, stored payloads, generated artifacts, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Metabase now reports Metabase 1.58.15, 1.59.12, 1.60.6.3, 1.61.1.4, or a later fixed release for the deployed branch or a later vendor-supported fixed release for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-59827, using a safe regression test or vendor-provided validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, credential exposure, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-59827?
metabase should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.