Is h2o 3.46 vulnerable?
PyPI · 12 releases from 3.46.0.1 to 3.46.0.12 · latest h2o is 3.46.0.12 · checked 20 Nov 2026
Yes: 1 known advisory
Yes. h2o 3.46.0.12, the last 3.46 release, is affected by 1 known security advisory (1 high), including CVE-2024-7768. 9 more affect earlier 3.46.x releases. At least one has no fixed release yet.
Is your project on an affected h2o?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting h2o 3.46.0.12
H2O Vulnerable to Denial of Service (DoS) via `/3/ImportFiles` Endpoint
- Affected
- <=3.46.1
- Fixed in
- No fix released
Fixed within 3.46.x, affecting earlier releases
No summary published
- Affected
- <3.46.0.10
- Fixed in
- 3.46.0.10
H2O has an External Control of File Name or Path vulnerability
- Affected
- <=3.46.0.1
- Fixed in
- No fix released
H2O affected by a deserialization vulnerability
- Affected
- <=3.46.0.7
- Fixed in
- No fix released
H2O Vulnerable to Denial of Service (DoS) via Large GZIP Parsing
- Affected
- >=3.32.1.2 <=3.46.0.2
- Fixed in
- No fix released
H2O Deserialization of Untrusted Data Vulnerability
- Affected
- <3.46.0.6
- Fixed in
- 3.46.0.6
H2O Vulnerable to Denial of Service (DoS) via `/3/ParseSetup` Endpoint
- Affected
- >=3.30.0.7 <=3.46.0.1
- Fixed in
- No fix released
H2O Vulnerable to Denial of Service (DoS) and File Write
- Affected
- >=3.34.0.1 <=3.46.0.1
- Fixed in
- No fix released
H2O Vulnerable to Denial of Service (DoS) via `/3/Parse` Endpoint
- Affected
- >=3.30.0.7 <=3.46.0.1
- Fixed in
- No fix released
H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL
- Affected
- <=3.46.0.7
- Fixed in
- No fix released
Every h2o 3.46.x release
Affected: 3.46.0.1 to 3.46.0.12.
| Version | Known advisories |
|---|---|
| h2o 3.46.0.12 | CVE-2024-7768 |
| h2o 3.46.0.11 | CVE-2024-7768 |
| h2o 3.46.0.10 | CVE-2024-7768 |
| h2o 3.46.0.9 | CVE-2026-3960, CVE-2024-7768 |
| h2o 3.46.0.8 | CVE-2026-3960, CVE-2024-7768 |
| h2o 3.46.0.7 | CVE-2026-3960, CVE-2025-6544, CVE-2024-7768, CVE-2024-45758 |
| h2o 3.46.0.6 | CVE-2026-3960, CVE-2025-6544, CVE-2024-7768, CVE-2024-45758 |
| h2o 3.46.0.5 | CVE-2026-3960, CVE-2025-6544, CVE-2024-7768, CVE-2024-10553, CVE-2024-45758 |
| h2o 3.46.0.4 | CVE-2026-3960, CVE-2025-6544, CVE-2024-7768, CVE-2024-10553, CVE-2024-45758 |
| h2o 3.46.0.3 | CVE-2026-3960, CVE-2025-6544, CVE-2024-7768, CVE-2024-10553, CVE-2024-45758 |
| h2o 3.46.0.2 | CVE-2026-3960, CVE-2025-6544, CVE-2024-7765, CVE-2024-7768, CVE-2024-10553, CVE-2024-45758 |
| h2o 3.46.0.1 | CVE-2026-3960, CVE-2024-5986, CVE-2025-6544, CVE-2024-7765, CVE-2024-7768, CVE-2024-10553, CVE-2024-10550, CVE-2024-10572, CVE-2024-10549, CVE-2024-45758 |
Which of your client projects are still on h2o 3.46?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact h2o version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other h2o versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.