CVE-2026-3960: h2oai/h2o-3 · Code Injection
Affects h2oai/h2o-3Source CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.46.0.10 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.46.0.10
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade h2oai/h2o-3 to 3.46.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| h2oaih2oai/h2o-3 | Affected
| Fixed in– |
GitHubh2oai/h2o-3pkg:github/h2oai/h2o-3Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade H2O-3 to version 3.46.0.10 or later, where this vulnerability is resolved. Since the vendor advisory or patch links are not explicitly provided, verify the upgrade availability from the official H2O-3 release notes or vendor site. No other mitigations are specified. Patch status is not explicitly confirmed in the input data, so check the vendor advisory for current remediation guidance.
Description
A critical remote code execution vulnerability exists in the unauthenticated REST API endpoint /99/ImportSQLTable in H2O-3 version 3.46.0.9 and prior. The vulnerability arises due to insufficient security controls in the parameter blacklist mechanism, which only targets MySQL JDBC driver-specific dangerous parameters. An attacker can bypass these controls by switching the JDBC URL protocol to jdbc:postgresql: and exploiting PostgreSQL JDBC driver-specific parameters such as socketFactory and socketFactoryArg. This allows unauthenticated attackers to execute arbitrary code on the H2O-3 server with the privileges of the H2O-3 process. The issue is resolved in version 3.46.0.10.