Metabase up to 1.58.14/1.59.11 H2 Database Query deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.59- |
Summary
A vulnerability identified as critical has been detected in Metabase up to 1.58.14/1.59.11. Affected by this vulnerability is an unknown functionality of the component H2 Database Query Handler. The manipulation leads to deserialization. This vulnerability is uniquely identified as CVE-2026-59827. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Metabase up to 1.58.14/1.59.11 and classified as critical. This issue affects some unknown functionality of the component H2 Database Query Handler. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-59827 since 07/07/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.58.15, 1.59.12, 1.60.6.3 or 1.61.1.4 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 1.58.0
- 1.58.1
- 1.58.2
- 1.58.3
- 1.58.4
- 1.58.5
- 1.58.6
- 1.58.7
- 1.58.8
- 1.58.9
- 1.58.10
- 1.58.11
- 1.58.12
- 1.58.13
- 1.58.14
- 1.59.0
- 1.59.1
- 1.59.2
- 1.59.3
- 1.59.4
- 1.59.5
- 1.59.6
- 1.59.7
- 1.59.8
- 1.59.9
- 1.59.10
- 1.59.11
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Metabase 1.58.15/1.59.12/1.60.6.3/1.61.1.4
Timeline
07/07/2026 CVE reserved07/09/2026 Advisory disclosed
07/09/2026 VulDB entry created
07/09/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-59827 (🔒)
GCVE (CVE): GCVE-0-2026-59827
GCVE (VulDB): GCVE-100-377267
Entry
Created: 07/09/2026 20:34Changes: 07/09/2026 20:34 (52)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.