Skip to main content
VulnerabilityPublished Updated

CVE-2025-6544: Ai.h2o:h2o core: H2O affected by a deserialization vulnerability

Affects ai.h2o:h2o-coreSource GCVE Database

0
Authoritative record:CVE-2025-6544· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical.

Data as of 27 Oct 2026, 17:29 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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
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, users should consider restricting access to the affected service and carefully validate or sanitize JDBC connection parameters to mitigate exploitation risk.

Description

A critical deserialization vulnerability (CVE-2025-6544) affects h2oai/h2o-3 versions up to 3.46.0.7. It allows attackers to read arbitrary system files and execute arbitrary code by exploiting improper handling of JDBC connection parameters. The vulnerability can be triggered by bypassing regular expression checks and using double URL encoding.

References

Community reviews

Loading reviews…