Advisory record · GHSA-wj3h-wx8g-x699

H2O has an External Control of File Name or Path vulnerability

CVSS 9.1 CriticalCriticalEPSS 0.0070 · 53rd percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

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.

PackageEcosystemAffectedFixed in
ai.h2o:h2o-coreMaven<=3.46.0.1No fixed version yet
h2oPyPI<=3.46.0.1No fixed version yet
Identifiers
GHSA-wj3h-wx8g-x699 · CVE-2024-5986 · PYSEC-2026-353
Weakness (CWE)
CWE-73
Published
2 Feb 2026
Updated
27 Oct 2026

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

ScoreRatingCVSSVectorSource
9.1 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H 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

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

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.