H2O affected by a deserialization vulnerability
A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.7, 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-6544US | — | — | ||
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 f… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/h2oai/h2o-3PACKAGE
- https://github.com/h2oai/h2o-3/commit/0298ee348f5c73673b7b542158081e79605f5f25WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/h2o/PYSEC-2026-349.yamlWEB
- https://huntr.com/bounties/53f35a0f-d644-4f82-93aa-89fe7e0aed40WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-6544ADVISORY
- https://pypi.org/project/h2oWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan