CVE-2024-10553 Jdbc Deserialization in h2oai/h2o-3
Unauthenticated attackers can execute arbitrary code via JDBC URL deserialization in H2O-3 REST API endpoints.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-10553?
CVE-2024-10553 is a critical unsafe deserialization vulnerability in h2oai/h2o-3, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitrary code via deserialization of untrusted data. The vulnerability exists in the endpoints POST /99/ImportSQLTable and POST /3/SaveToHiveTable, where user-controlled JDBC URLs are passed to DriverManager.getConnection, leading to deserialization if a MySQL or PostgreSQL driver is available in the classpath. This issue is fixed in version 3.47.0.
Weakness: CWE-502
Which versions are affected by CVE-2024-10553?
5 open source packages ship an affected version, including h2o and ai.h2o:h2o-core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
h2o PyPI | All versions | 3.46.0.6 |
h2o PyPI | All versions | 3.46.0.6 |
h2o PyPI | All versions | 3.46.0.6 |
ai.h2o:h2o-core Maven | All versions | 3.46.0.6 |
ai.h2o:h2o-core Maven | All versions | 3.46.0.6 |
Products include H2o H2o.
How do I fix CVE-2024-10553?
Upgrade h2o to 3.46.0.6 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2024-10553 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10553 exists.
Other vulnerabilities in h2oai/h2o-3
Sources
Also known as GHSA-h7xg-cmpp-48hf, PYSEC-2026-351.