Skip to main content
VulnerabilityPublished Updated

CVE-2024-45758: Ai.h2o:h2o core: H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL

Affects ai.h2o:h2o-coreSource GCVE Database

0
Authoritative record:CVE-2024-45758· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical.

Data as of 27 Oct 2026, 18:29 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenai.h2o:h2o-coreAffected
  • <=3.46.0.7
Fixed in–
PyPIh2oAffected
  • <=3.46.0.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the ImportSQLTable URI endpoint to trusted users only and monitor for suspicious POST requests containing JDBC connection URLs.

Description

H2O.ai H2O versions up to 3.46.0.7 are vulnerable to deserialization attacks via the JDBC Connection URL. An attacker able to send a POST request to the ImportSQLTable URI with a crafted JSON payload containing a malicious connection_url can exploit this flaw. This vulnerability allows arbitrary code execution and unauthorized file reads without requiring authentication.

References

Community reviews

Loading reviews…