Code Injection in ai.h2o:h2o-core (CVE-2026-3960)
Summary
Code injection in ai.h2o:h2o-core (CVE-2026-3960). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.46.0.10 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3960 has been found in ai.h2o:h2o-core.
Risk of unauthorized operations or information disclosure. CVSS score: 9.8/10.
What to do: upgrade ai.h2o:h2o-core to 3.46.0.10 or later.
If unsure, ask your IT team or search "ai.h2o:h2o-core CVE-2026-3960" on the vendor's site.
CVE-2026-3960 (ai.h2o:h2o-core) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.46.0.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in ai.h2o:h2o-core.
Check the vendor advisory for the affected versions of ai.h2o:h2o-core.
Severity: Critical (CVSS 9.8/10). Risk of unauthorized operations or information disclosure.
Update to 3.46.0.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで ai.h2o:h2o-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade ai.h2o:h2o-core to 3.46.0.10ステージング環境で 3.46.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web huntr.com