© 2025-2026 PySpect
No release of h2o is currently known to be free of vulnerabilities.
A critical remote code execution vulnerability exists in the unauthenticated REST API endpoint /99/ImportSQLTable in H2O-3 version 3.46.0.9 and prior. The vulnerability arises due to insufficient security controls in the parameter blacklist mechanism, which only targets MySQL JDBC driver-specific dangerous parameters. An attacker can bypass these controls by switching the JDBC URL protocol to jdbc:postgresql: and exploiting PostgreSQL JDBC driver-specific parameters such as socketFactory and socketFactoryArg. This allows unauthenticated attackers to execute arbitrary code on the H2O-3 server with the privileges of the H2O-3 process. The issue is resolved in version 3.46.0.10.
Fixed in: 3.46.0.10
H2O has an External Control of File Name or Path vulnerability
H2O affected by a deserialization vulnerability
H2O Vulnerable to Arbitrary File Overwrite
H2O Vulnerable to Denial of Service (DoS) via `HEAD` Request
H2O Vulnerable to Denial of Service (DoS) via Large GZIP Parsing
H2O Vulnerable to Denial of Service (DoS) via `/3/ImportFiles` Endpoint
H2O Vulnerable to Arbitrary File Overwrite via File Export
H2O Vulnerable to Execution of Arbitrary Files
H2O Vulnerable to Denial of Service (DoS) via `/3/ParseSetup` Endpoint
H2O Deserialization of Untrusted Data Vulnerability
Fixed in: 3.46.0.6
H2O Vulnerable to Denial of Service (DoS) and File Write
H2O Vulnerable to Denial of Service (DoS) via `/3/Parse` Endpoint
H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL
h2o vulnerable to unexpected POST request shutting down server
Arbitrary system path lookup in h20
External Control of File Name or Path in h2oai/h2o-3
Fixed in: 3.46.0.1