CVE-2024-45758Critical· 9.1▾ MidnightH2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 50.1 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 27.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.9%
H2O.ai H2O through 3.46.0.4 allows attackers to arbitrarily set the JDBC URL, leading to deserialization attacks, file reads, and command execution. Exploitation can occur when an attacker has access to post to the ImportSQLTable URI with a JSON document containing a connection_url property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors.
ai.h2o:h2o-core <= 3.46.0.7h2o <= 3.46.0.7Refer to the advisory for the patched release.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-5986Critical· 9.1H2O has an External Control of File Name or Path vulnerability
CVE-2025-6544Critical· 9.8A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.8, allowing attackers to read arbitrary system files and execute arbitrary code
CVE-2024-10553Critical· 9.8H2O Deserialization of Untrusted Data Vulnerability
CVE-2023-6569Critical· 9.3External Control of File Name or Path in h2oai/h2o-3
CVE-2025-10768Medium· 6.3A flaw has been found in h2oai h2o-3 up to 3.46.08
CVE-2024-5550Medium· 5.3Arbitrary system path lookup in h20