Arbitrary Code Injection Affecting ai.h2o:h2o-core package, versions [,3.46.0.10)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-AIH2O-16417170
- published4 May 2026
- disclosed24 Apr 2026
- creditWhippet
Introduced: 24 Apr 2026
NewCVE-2026-3960 (opens in a new tab)How to fix?
Upgrade ai.h2o:h2o-core to version 3.46.0.10 or higher.
Overview
Affected versions of this package are vulnerable to Arbitrary Code Injection through the SQLManager.validateJdbcUrl logic in SQLManager. An attacker can trigger unsafe JDBC connection handling by supplying a PostgreSQL URL with dangerous parameters such as socketFactory, sslfactory, or loggerFile. This lets an attacker steer the JDBC driver into loading attacker-controlled classes or writing to attacker-chosen files, putting the application at risk of remote code execution or local file abuse when it accepts untrusted connection strings.
Notes
- The vulnerable blacklist is a static denylist in
SQLManager.validateJdbcUrl, so any deployment that accepts user-supplied JDBC URLs inherits the risk regardless of which higher-level import or connection workflow supplies the string.