# H2O has an External Control of File Name or Path vulnerability

Advisory record · `GHSA-wj3h-wx8g-x699`

- **Identifiers:** `GHSA-wj3h-wx8g-x699` · `CVE-2024-5986` · `PYSEC-2026-353`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-73](https://cwe.mitre.org/data/definitions/73.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 2 Feb 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Feb 2026, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `ai.h2o:h2o-core` (Maven): affected `<=3.46.0.1`; no fixed version yet
- `h2o` (PyPI): affected `<=3.46.0.1`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected packages are ai.h2o:h2o-core on Maven and h2o on PyPI, at versions up to and including 3.46.0.1, and the source lists no fixed version. A remote attacker with network access to the H2O server can write arbitrary data to any file on that server, which the source says could lead to remote code execution or full system access. The source gives no fixed version, so no upgrade target is listed; check the project's advisory for any mitigation guidance.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`, from CNA (@huntr_ai)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0070, the 53rd percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:07 UTC: First seen by agentprime
- 31 Oct 2026, 14:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wj3h-wx8g-x699)

## Sources

- [GitHub Advisory Database: GHSA-wj3h-wx8g-x699](https://github.com/advisories/GHSA-wj3h-wx8g-x699)
- [OSV: GHSA-wj3h-wx8g-x699](https://osv.dev/vulnerability/GHSA-wj3h-wx8g-x699)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-5986>
- <https://github.com/h2oai/h2o-3>
- <https://github.com/pypa/advisory-database/tree/main/vulns/h2o/PYSEC-2026-353.yaml>
- <https://huntr.com/bounties/64ff5319-6ac3-4447-87f7-b53495d4d5a3>
- <https://pypi.org/project/h2o>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wj3h-wx8g-x699>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wj3h-wx8g-x699/>. Everything for agents: <https://agentprime.io/llms.txt>.