Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven🐍 PyPI

CVE-2025-6544

CRITICAL

CVE-2025-6544 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in ai.h2o:h2o-core. O3 Security confirms whether CVE-2025-6544 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Deserialization Vulnerability in h2oai/h2o-3

Also known asGHSA-5w3j-gwgh-4rfvPYSEC-2026-349
Published
Sep 21, 2025
Updated
Jul 22, 2026
Affected
2 pkgs
Patched
None yet
Exploits
None indexed

Blast Radius

2 pkgs affected
ai.h2o:h2o-core🐍h2o

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
Mavenai.h2o:h2o-coreall versionsNo fix
🐍PyPIh2oall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ai.h2o:h2o-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of ai.h2o:h2o-core has shipped for CVE-2025-6544 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-6544 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-6544. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-6544 in your dependencies?

O3 detects CVE-2025-6544 across Maven, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.