PYSEC-2026-2180
Vulnerability from pysec - Published: 2026-04-23 10:16 - Updated: 2026-07-13 05:49
VLAI
Details
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.
Severity
9.8 (Critical)
Impacted products
| Name | purl | h2o | pkg:pypi/h2o |
|---|
Aliases
{
"affected": [
{
"ecosystem_specific": {},
"package": {
"ecosystem": "PyPI",
"name": "h2o",
"purl": "pkg:pypi/h2o"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.46.0.10"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.10.0.10",
"3.10.0.3",
"3.10.0.6",
"3.10.0.7",
"3.10.0.8",
"3.10.3.3",
"3.10.3.4",
"3.10.4.1",
"3.10.4.2",
"3.10.4.3",
"3.10.4.4",
"3.10.4.6",
"3.10.4.8",
"3.16.0.1",
"3.16.0.2",
"3.16.0.3",
"3.16.0.4",
"3.18.0.1",
"3.18.0.10",
"3.18.0.11",
"3.18.0.2",
"3.18.0.3",
"3.18.0.4",
"3.18.0.5",
"3.18.0.6",
"3.18.0.7",
"3.18.0.8",
"3.18.0.9",
"3.20.0.4",
"3.20.0.5",
"3.20.0.6",
"3.20.0.7",
"3.20.0.8",
"3.22.0.1",
"3.22.0.2",
"3.22.0.3",
"3.22.0.4",
"3.22.0.5",
"3.22.1.1",
"3.22.1.2",
"3.22.1.3",
"3.22.1.4",
"3.22.1.5",
"3.22.1.6",
"3.24.0.1",
"3.24.0.2",
"3.24.0.3",
"3.24.0.4",
"3.24.0.5",
"3.26.0.1",
"3.26.0.10",
"3.26.0.11",
"3.26.0.2",
"3.26.0.3",
"3.26.0.4",
"3.26.0.5",
"3.26.0.6",
"3.26.0.8",
"3.26.0.9",
"3.28.0.1",
"3.28.0.2",
"3.28.0.3",
"3.28.1.2",
"3.28.1.3",
"3.30.0.1",
"3.30.0.2",
"3.30.0.3",
"3.30.0.4",
"3.30.0.5",
"3.30.0.6",
"3.30.0.7",
"3.30.1.1",
"3.30.1.2",
"3.30.1.3",
"3.32.0.2",
"3.32.0.3",
"3.32.0.4",
"3.32.0.5",
"3.32.1.1",
"3.32.1.2",
"3.32.1.3",
"3.32.1.4",
"3.32.1.5",
"3.32.1.6",
"3.32.1.7",
"3.34.0.3",
"3.34.0.7",
"3.34.0.8",
"3.36.0.2",
"3.36.0.3",
"3.36.0.4",
"3.36.1.1",
"3.36.1.2",
"3.36.1.3",
"3.36.1.4",
"3.36.1.5",
"3.38.0.1",
"3.38.0.2",
"3.38.0.3",
"3.38.0.4",
"3.40.0.1",
"3.40.0.2",
"3.40.0.3",
"3.40.0.4",
"3.42.0.1",
"3.42.0.2",
"3.42.0.3",
"3.42.0.4",
"3.44.0.1",
"3.44.0.2",
"3.44.0.3",
"3.46.0.1",
"3.46.0.2",
"3.46.0.3",
"3.46.0.4",
"3.46.0.5",
"3.46.0.6",
"3.46.0.7",
"3.46.0.8",
"3.46.0.9"
]
}
],
"aliases": [
"CVE-2026-3960"
],
"details": "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.",
"id": "PYSEC-2026-2180",
"modified": "2026-07-13T05:49:05.335112Z",
"published": "2026-04-23T10:16:17.813Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/h2oai/h2o-3/commit/b9ae2d3c5220db2dc53753357a783e590364d044"
},
{
"type": "EVIDENCE",
"url": "https://huntr.com/bounties/6954fe04-b905-453f-8c53-205ac8377e0d"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…