CVE-2023-6569 json
External Control of File Name or Path in h2oai/h2o-3
published 2023-12-14 2 y ago modified 2026-10-27 12 d ago also GHSA-gqrq-j6pm-98c2 , PYSEC-2026-350 , EUVD-2023-3215
- cvss
- 9.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
External Control of File Name or Path in h2oai/h2o-3
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/a5d003dc-c23e-4c98-8dcf-35ba9252fa3c referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| GitHub | 3.0 | 9.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H |
| OSV | 3.0 | 9.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | h2o | <3.46.0.1 |
3.46.0.1 |
Affected products
- h2oai h2oai/h2o-3
Classification
References
-
github.com
/h2oai/h2o-3/commit/e8884f5187eb81311877c5f0dd4d6d9c70f33d78
web
-
huntr.com
/bounties/a5d003dc-c23e-4c98-8dcf-35ba9252fa3c
web, exploit
-
nvd.nist.gov
/vuln/detail/CVE-2023-6569
advisory
-
github.com
/h2oai/h2o-3
package
-
github.com
/pypa/advisory-database/tree/main/vulns/h2o/PYSEC-2026-350.yaml
web
-
pypi.org
/project/h2o
web, package
-
github.com
/advisories/GHSA-gqrq-j6pm-98c2
advisory
Sources
- CVE List CVE-2023-6569
- GitHub Advisory GHSA-gqrq-j6pm-98c2
- NVD CVE-2023-6569
- OSV PYSEC-2026-350
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.