CriticalGHSA-gqrq-j6pm-98c2CVE-2023-6569PYSEC-2026-350

External Control of File Name or Path in h2oai/h2o-3

Published 14 Dec 2023 · Updated 27 Oct 2026

Is your project on an affected h2o?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

h2oPyPI
Affected
<3.46.0.1
Fixed in
3.46.0.1
Update to the fixed version for your release line, for example:pip install 'h2o>=3.46.0.1'

Details

Remote unauthenticated attackers can overwrite arbitrary server files with attacker-controllable data. The data that the attacker can control is not entirely arbitrary. h2o writes a CSV/XLS/etc file to disk, so the attacker data is wrapped in quotations and starts with "C1", if they're exporting as CSV.

Is GHSA-gqrq-j6pm-98c2 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected h2o, and gives you the command that fixes it.

More advisories for h2o

  • LowCVE-2026-3960No summary published · 23 Apr 2026
  • CriticalCVE-2024-5986H2O has an External Control of File Name or Path vulnerability · 2 Feb 2026
  • CriticalCVE-2025-6544H2O affected by a deserialization vulnerability · 22 Sept 2025
  • HighCVE-2024-8616H2O Vulnerable to Arbitrary File Overwrite · 20 Mar 2025
  • HighCVE-2024-8062H2O Vulnerable to Denial of Service (DoS) via `HEAD` Request · 20 Mar 2025
  • HighCVE-2024-7765H2O Vulnerable to Denial of Service (DoS) via Large GZIP Parsing · 20 Mar 2025
All 17 advisories for h2o

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.