h2o
16 published advisories; version 3.46.0.6 or later fixes all but 14 of them.
- Registry
- PyPI
- Advisories
- 16
- Latest fix
- 3.46.0.6
- Exploited in the wild
- None listed
14 advisories have no fixed release in any version yet. What can be done meanwhile:
General guidance from ShieldPi, not a vendor fix
- Command or code injection. Remove or disable the affected server or tool, or run it in a sandbox with no secrets in its environment.GHSA-wjpv-64v2-2qpq · GHSA-58m3-rcvp-f9ww
- Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.GHSA-wj3h-wx8g-x699 · GHSA-47f6-5p7h-5f3h · GHSA-g48v-3p35-88jr · GHSA-x234-r5fg-x52m
- Unsafe deserialization. Do not let it load files, models or data from sources you do not trust, and keep its RPC and socket ports reachable only from localhost or hosts you trust.GHSA-5w3j-gwgh-4rfv · GHSA-hrmc-jmp7-mpm2
Check your projects
shieldpi agent-config checks agent and MCP packages from npm and PyPI, not h2o. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.
osv-scanner scan source -r .Or check a lockfile against ShieldMap in your browser.
Source: github.com/h2oai/h2o-3, named in the package metadata (not verified)
0 of the last 10 releases of h2o were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 3.46.0.12
- 3.46.0.11
- 3.46.0.10
- 3.46.0.9
- 3.46.0.8
- 3.46.0.7
- 3.46.0.6
- 3.46.0.5
- 3.46.0.4
- 3.46.0.3
Green: published with provenance. Grey: without.
OpenSSF Scorecard: 5.7 of 10 on 2026-11-16.
- No dangerous CI workflows
- 10/10
- CI tokens read-only by default
- 0/10
- Build dependencies pinned
- 0/10
- Branch protection
- Not checked
- Changes reviewed before merge
- 1/10
- Signed releases
- Not checked
- Actively maintained
- 10/10
- Security policy
- 10/10
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
| Advisory | Severity | Affected | Fixed in | Published |
|---|---|---|---|---|
| H2O has an External Control of File Name or Path vulnerabilityCVE-2024-5986 | Critical | <= 3.46.0.1 | No fix yet | 2026-02-02 |
| H2O affected by a deserialization vulnerabilityCVE-2025-6544 | Critical | <= 3.46.0.7 | No fix yet | 2025-09-22 |
| H2O Vulnerable to Arbitrary File Overwrite via File ExportCVE-2024-6854 | High | >= 3.32.1.1, <= 3.46.0 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Denial of Service (DoS) via `HEAD` RequestCVE-2024-8062 | High | >= 3.2.0.1, <= 3.46.0 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Denial of Service (DoS) via Large GZIP ParsingCVE-2024-7765 | High | >= 3.32.1.2, <= 3.46.0.2 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Denial of Service (DoS) via `/3/ParseSetup` EndpointCVE-2024-10550 | High | >= 3.30.0.7, <= 3.46.0.1 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Arbitrary File OverwriteCVE-2024-8616 | High | >= 3.10.4.1, <= 3.46.0 | No fix yet | 2025-03-20 |
| H2O Deserialization of Untrusted Data VulnerabilityCVE-2024-10553 | Critical | < 3.46.0.6 | 3.46.0.6 | 2025-03-20 |
| H2O Vulnerable to Execution of Arbitrary FilesCVE-2024-6863 | Medium | >= 3.32.1.2, <= 3.46.0 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Denial of Service (DoS) via `/3/ImportFiles` EndpointCVE-2024-7768 | High | <= 3.46.1 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Denial of Service (DoS) and File WriteCVE-2024-10572 | High | >= 3.34.0.1, <= 3.46.0.1 | No fix yet | 2025-03-20 |
| H2O Vulnerable to Denial of Service (DoS) via `/3/Parse` EndpointCVE-2024-10549 | High | >= 3.30.0.7, <= 3.46.0.1 | No fix yet | 2025-03-20 |
| H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URLCVE-2024-45758 | Critical | <= 3.46.0.7 | No fix yet | 2024-09-06 |
| h2o vulnerable to unexpected POST request shutting down serverCVE-2024-5979 | High | <= 3.46.0 | No fix yet | 2024-06-27 |
| Arbitrary system path lookup in h20CVE-2024-5550 | Medium | <= 3.40.0.4 | No fix yet | 2024-06-06 |
| External Control of File Name or Path in h2oai/h2o-3CVE-2023-6569 | Critical | < 3.46.0.1 | 3.46.0.1 | 2023-12-14 |
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].