# CVE-2023-6569: External Control of File Name or Path in h2oai/h2o-3

> Attackers can manipulate file paths to read or modify arbitrary files in the H2O-3 machine learning library.

- **Severity:** Critical 9.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2023
- **Updated:** 22 May 2025
- **Also known as:** GHSA-gqrq-j6pm-98c2, PYSEC-2026-350

## What is CVE-2023-6569?

CVE-2023-6569 is a critical path traversal vulnerability in h2oai/h2o-3, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2023-6569?

3 open source packages ship an affected version, including h2o. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `h2o` | PyPI | All versions | 3.46.0.1 |
| `h2o` | PyPI | All versions | 3.46.0.1 |
| `h2o` | PyPI | All versions | 3.46.0.1 |

Products: H2o H2o.

## How do I fix CVE-2023-6569?

Upgrade h2o to 3.46.0.1 or later.

## Is CVE-2023-6569 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6569 exists.

## Other vulnerabilities in h2oai/h2o-3

- [CVE-2023-6016](https://insights.sbomify.com/CVE-2023-6016/): H2O Remote Code Execution via POJO Model Import (critical 10.0)
- [CVE-2025-6544](https://insights.sbomify.com/CVE-2025-6544/): Deserialization Vulnerability in h2oai/h2o-3 (critical 9.8)
- [CVE-2024-10553](https://insights.sbomify.com/CVE-2024-10553/): Jdbc Deserialization in h2oai/h2o-3 (critical 9.8)
- [CVE-2023-6013](https://insights.sbomify.com/CVE-2023-6013/): H2O Local File Include (critical 9.3)
- [CVE-2023-6038](https://insights.sbomify.com/CVE-2023-6038/): Local File Inclusion in h2oai/h2o-3 (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6569 and fix it if it is affected.

What it is: CVE-2023-6569 is a critical path traversal vulnerability in h2oai/h2o-3, published on 14 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6569 exists.

Affected packages and fixed versions:
- h2o (PyPI): affected all versions; fixed in 3.46.0.1
- h2o (PyPI): affected all versions; fixed in 3.46.0.1
- h2o (PyPI): affected all versions; fixed in 3.46.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6569/ (Markdown: https://insights.sbomify.com/CVE-2023-6569/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6569
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6569
- OSV: https://osv.dev/vulnerability/CVE-2023-6569

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6569/
Summaries are generated and may contain mistakes; the official description above is the record.