CVE-2026-59827
Authenticated H2 native query RCE in Metabase via unsafe Java deserialization
Is CVE-2026-59827 being exploited?
Not confirmed. CVE-2026-59827 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 3.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-59827?
CVE-2026-59827 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-59827?
Yes. A fix has been recorded for CVE-2026-59827. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59827 affect?
CVE-2026-59827 affects Metabase < 1.58.15, Metabase < 1.59.12, Metabase < 1.60.6.3, Metabase < 1.61.1.4, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59827?
Upgrade to 1.58.15/1.59.12/1.60.6.3/1.61.1.4; disable H2/native queries and restrict DB access until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker who can run H2 native queries can deserialize arbitrary Java objects and achieve remote code execution on the Metabase server.
Immediate action required
- affected>= 1.58.0 and < 1.58.15
- affected>= 1.59.0 and < 1.59.12
- affected>= 1.60.0 and < 1.60.6.3
- affected>= 1.61.0 and < 1.61.1.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.