Skip to main content
VulnerabilityPublished Updated

CVE-2025-10769: h2oai h2o-3 · Deserialization

Affects h2oai h2o-3Source CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
h2oai h2o-3Affected
  • =3.46.08
Fixed in–

AI-suggested

European organizations should immediately audit their use of h2o-3, specifically checking for versions up to 3.46.08. 2) Implement strict input validation and sanitization on any user-supplied parameters, especially those related to JDBC connection URLs, to prevent malicious deserialization payloads. 3) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to detect and block suspicious deserialization patterns or anomalous requests targeting the /99/ImportSQLTable endpoint. 4) Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected deserialization operations or abnormal JDBC connection strings. 5) Consider isolating the h2o-3 environment in a sandbox or container with minimal privileges to limit potential damage from exploitation. 6) Engage with the vendor or community to track any forthcoming patches or updates and plan for timely application once available. 7) Review and tighten access controls to ensure only authorized users have privileges that could be leveraged for exploitation (noting the PR:L requirement).

Description

A vulnerability has been found in h2oai h2o-3 up to 3.46.08. This affects an unknown function of the file /99/ImportSQLTable of the component H2 JDBC Driver. Such manipulation of the argument connection_url leads to deserialization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…