CVE-2026-59827
CVE-2026-59827 — Metabase: Unsafe Deserialization of H2 Query Results
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.
Published Updated Sources: NVD, metabase (CNA), GitHub, Exploit-DB
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Reported
not confirmed by CISA
EPSS
4%
chance of exploitation in 30 days
CVSS base
8.8
high · 2 sources
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade metabase to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| metabase | metabase | >= 1.58.0, < 1.58.15 | Vulnerable |
| metabase | metabase | >= 1.59.0, < 1.59.12 | Vulnerable |
| metabase | metabase | >= 1.60.0, < 1.60.6.3 | Vulnerable |
| metabase | metabase | >= 1.61.0, < 1.61.1.4 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
Low
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 9.9 | CVSS 3.1 | critical | 3.1 | 6 | GitHub (CNA), metabase (CNA) |
| 8.8 | CVSS 3.1 | high | 2.8 | 5.9 | NVD |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness & attack patterns
- CWE-502Deserialization of Untrusted Data
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
5
2 of the 5 sampled are weaponized
Exploit entries
1
Exploit-DB and CTI exploit indexes
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable metabase.
- Monitor for scanner or exploit-pattern traffic after 6 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · webapps entry: Metabase 0.61.0 - Authenticated Remote Code Execution
Sep 3, 2026 · Exploit-DB
Added · CVSS 3.1 8.8 (AV:N)
Jul 13, 2026 · NVD
Initial · CVE published
Jul 9, 2026 · NVD
References
7 on the record
- github.com/metabase/metabase/commit/00f42511fe3bc4385652a2e96862ee6fd7d42cf8
Patch
- github.com/metabase/metabase/releases/tag/v0.58.15
Release Notes
- github.com/metabase/metabase/releases/tag/v0.59.12
Release Notes
- github.com/metabase/metabase/releases/tag/v0.60.6.3
Release Notes
- github.com/metabase/metabase/releases/tag/v0.61.1.4
Release Notes
- github.com/metabase/metabase/security/advisories/GHSA-w95f-x9v9-wv36
Vendor Advisory
- www.exploit-db.com/exploits/52680
Vendor Advisory
Elsewhere on this site
- metabaseevery CVE for this vendor
- Deserializationsame class
- CWE-502other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-59827 is Metabase: Unsafe Deserialization of H2 Query Results, a high vulnerability affecting metabase from metabase. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 6 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 4% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.