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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2024-45758: 0.91% estimated exploitation activity in the next 30 days; percentile 59.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

H2O.ai H2O through 3.46.0.4 allows attackers to arbitrarily set the JDBC URL, leading to deserialization attacks, file reads, and command execution. Exploitation can occur when an attacker has access to post to the ImportSQLTable URI with a JSON document containing a connection_url property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors.

Published by the source

6 Sep 2024, 18:31 UTC

Last modified by the source

27 Oct 2026, 17:45 UTC

Source last checked

28 Oct 2026, 06:05 UTC

1. Revision 4 · amended · 28 Oct 2026

   Amended from osv record GHSA-hrmc-jmp7-mpm2

2. Revision 3 · amended · 27 Oct 2026

   Amended from ghsa record GHSA-hrmc-jmp7-mpm2

3. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hrmc-jmp7-mpm2

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hrmc-jmp7-mpm2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-45758

Advisory: H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL
IDs: CVE-2024-45758, GHSA-hrmc-jmp7-mpm2
Record: https://patchnext.com/advisories/cve-2024-45758 (revision 4, source checked 28 Oct 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI h2o: affected <= 3.46.0.7
- Maven ai.h2o:h2o-core: affected <= 3.46.0.7

## Suggested inspection (read-only)
- `python -m pip show h2o`: prints the installed version. Run with the environment that serves production active.
- Maven ai.h2o:h2o-core: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on h2o, ai.h2o:h2o-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hrmc-jmp7-mpm2 (OSV record GHSA-hrmc-jmp7-mpm2 lists affected ranges: Maven ai.h2o:h2o-core >=0 =0 <=3.46.0.7)
- Verified: https://github.com/advisories/GHSA-hrmc-jmp7-mpm2 (GitHub-reviewed advisory GHSA-hrmc-jmp7-mpm2 lists affected ranges: Maven ai.h2o:h2o-core >=0 =0 <=3.46.0.7)

Commands are suggestions: review each one before running it.