Advisory record · GHSA-hrmc-jmp7-mpm2

H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL

CVSS 9.1 CriticalCriticalEPSS 0.0091 · 60th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 6 Sept 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ai.h2o:h2o-coreMaven<=3.46.0.7No fixed version yet
h2oPyPI<=3.46.0.7No fixed version yet
Identifiers
GHSA-hrmc-jmp7-mpm2 · CVE-2024-45758 · PYSEC-2026-352
Weakness (CWE)
CWE-502
Published
6 Sept 2024
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

H2O.ai H2O (Maven ai.h2o:h2o-core and PyPI h2o, versions up to and including 3.46.0.7 per the package listings; the source describes issues through 3.46.0.4) lets a remote requester set the JDBC connection URL used for SQL table import. An attacker who can send requests to that import endpoint can use a crafted connection URL to trigger deserialization, read files, and run commands. No fixed version is listed in the source.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0091, the 60th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.