CVE-2025-6544: H2O affected by a deserialization vulnerability
A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.7, allowing attackers to read arbitrary system files and execute arbitrary code. The vulnerability arises from improper handling of JDBC connection parameters, which can be exploited by bypassing regular expression checks and using double URL encoding. This issue impacts all users of the affected versions.
Published Sep 22, 2025
Affected packages
ai.h2o:h2o-core
- Ecosystem
- Maven
- Affected
- <= 3.46.0.7
- Fixed in
- No patched version yet
- Check
mvn dependency:tree -Dincludes=ai.h2o:h2o-core
h2o
- Ecosystem
- PyPI
- Affected
- <= 3.46.0.7
- Fixed in
- No patched version yet
- Check
pip show h2o
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.7, allowing attackers to read arbitrary system files and execute arbitrary code. The vulnerability arises from improper handling of JDBC connection parameters, which can be exploited by bypassing regular expression checks and using double URL encoding. This issue impacts all users of the affected versions.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Maven vulnerabilities
All Maven entriesCVE-2024-5986
H2O has an External Control of File Name or Path vulnerability
critical9.1No fixFeb 2, 2026CVE-2024-10553
H2O Deserialization of Untrusted Data Vulnerability
critical9.8Mar 20, 2025CVE-2024-45758
H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL
critical9.1No fixSep 6, 2024
