Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2024-10553

CRITICALFix: h2oai/h2o-3@ac1d642

CVE-2024-10553 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in ai.h2o:h2o-core. O3 Security confirms whether CVE-2024-10553 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Jdbc Deserialization in h2oai/h2o-3

Also known asGHSA-h7xg-cmpp-48hfPYSEC-2026-351
Published
Mar 20, 2025
Updated
Jul 22, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Jul 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
ai.h2o:h2o-core🐍h2o

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenai.h2o:h2o-coreall versions3.46.0.6
🐍PyPIh2oall versions3.46.0.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ai.h2o:h2o-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ai.h2o:h2o-core to 3.46.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-10553 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-10553 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-10553. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-10553 in your dependencies?

O3 detects CVE-2024-10553 across Maven, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2024-10553: Jdbc Deserialization in… | O3 Security