CVE-2025-5662: h2oai/h2o-3 · Deserialization of Untrusted Data
Affects h2oai/h2o-3Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.46.0.8 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.46.0.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade h2oai/h2o-3 to 3.46.0.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| h2oai h2oai/h2o-3 | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-5662, European organizations should immediately upgrade to h2oai/h2o-3 version 3.46.0.8 or later, where the vulnerability is patched. If immediate upgrade is not feasible, organizations should restrict network access to the vulnerable REST API endpoints by implementing strict firewall rules and network segmentation to limit exposure only to trusted hosts. Additionally, monitoring and logging of API requests should be enhanced to detect anomalous or suspicious deserialization attempts. Organizations should verify that the MySQL JDBC Driver is updated beyond version 8.0.19 and that the JDK version is upgraded beyond 8u112 to versions that address known deserialization issues. Employing runtime application self-protection (RASP) or web application firewalls (WAF) with deserialization attack detection capabilities can provide additional layers of defense. Finally, organizations should conduct thorough audits of their H2O-3 deployments and associated data pipelines to identify any signs of compromise and ensure secure configuration management practices are in place for all machine learning infrastructure components.
Description
A deserialization vulnerability exists in the H2O-3 REST API (POST /99/ImportSQLTable) that affects all versions up to 3.46.0.7. This vulnerability allows remote code execution (RCE) due to improper validation of JDBC connection parameters when using a Key-Value format. The vulnerability is present in the MySQL JDBC Driver version 8.0.19 and JDK version 8u112. The issue is resolved in version 3.46.0.8.