CVE-2025-6544: H2O Deserialization Vulnerability Leading to Arbitrary Code Execution

h2o Updated 29 Jun 2026

Summary

29/06/2026
No i
Critical
9.8

CVE-2025-6544: H2O affected by a deserialization vulnerability. Affects h2o versions < 3.46.0.7. No fix is published. How to fix ↓

Also tracked for

The same CVE-2025-6544 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

H2O is an open-source machine learning platform designed for data analysis and predictive modeling. It provides a user-friendly interface and supports various algorithms for data processing. However, versions of H2O up to 3.46.0.7 are vulnerable to a deserialization issue that can be exploited by attackers, potentially compromising system security.

Vulnerability Detail

A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.7, allowing attackers to read arbitrary system files and execute arbitrary code. This vulnerability arises from improper handling of JDBC connection parameters, which can be exploited by bypassing regular expression checks and using double URL encoding. The ramifications include unauthorized access to sensitive data and the ability to execute malicious code on the affected system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, avoid using JDBC connection parameters that could be manipulated. Ensure that any user inputs are properly sanitized and validated to prevent exploitation of this vulnerability.

Conclusion

The deserialization vulnerability in H2O poses a serious risk to users of affected versions. It is crucial to update to the latest version to mitigate potential security threats. Regular monitoring of dependencies using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for h2o →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 9.8, indicating a critical level of severity.

All versions of H2O up to and including 3.46.0.7 are affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Exploitation of this vulnerability can lead to unauthorized access to system files and execution of arbitrary code, posing significant security risks.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the Pipfile.lock.

Related vulnerabilities

Recent vulnerabilities recorded for h2o.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback