Skip to main content
VulnerabilityPublished Updated

CVE-2025-6544: h2oai/h2o-3 · Deserialization of Untrusted Data

Affects h2oai/h2o-3Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2025

  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
h2oai h2oai/h2o-3Affected
  • <=3.46.0.8
Fixed in–

AI-suggested

Organizations should immediately assess their deployment of h2oai/h2o-3 and identify any instances running versions up to 3.46.0.8. In the interim, organizations should implement strict input validation and sanitization on all JDBC connection parameters, employing allowlists and rejecting suspicious or double-encoded inputs. Network-level protections such as web application firewalls (WAFs) should be configured to detect and block malicious payloads targeting deserialization flaws and unusual URL encoding patterns. Restricting access to the h2o-3 service to trusted internal networks or VPNs can reduce exposure. Additionally, applying the principle of least privilege to the service account running h2o-3 can limit the potential damage from exploitation. Continuous monitoring for anomalous behavior and deploying endpoint detection and response (EDR) tools can help identify exploitation attempts early. Finally, organizations should prepare incident response plans specific to deserialization attacks and ensure backups are current and secure.

Description

A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.8, allowing attackers to read arbitrary system files and execute arbitrary code. The vulnerability arises from improper handling of JDBC connection parameters, which can be exploited by bypassing regular expression checks and using double URL encoding. This issue impacts all users of the affected versions.

References

Community reviews

Loading reviews…