# CVE-2024-6854: Arbitrary File Overwrite in h2oai/h2o-3

> An attacker can overwrite arbitrary files on the server by exploiting unrestricted export locations in the model export endpoint.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-47f6-5p7h-5f3h, PYSEC-2026-1436

## What is CVE-2024-6854?

CVE-2024-6854 is a high-severity path traversal vulnerability in h2oai/h2o-3, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In h2oai/h2o-3 version 3.46.0, the endpoint for exporting models does not restrict the export location, allowing an attacker to export a model to any file in the server's file structure, thereby overwriting it. This vulnerability can be exploited to overwrite any file on the target server with a trained model file, although the content of the overwrite is not controllable by the attacker.

Weakness: CWE-36 (Absolute Path Traversal)

## Which versions are affected by CVE-2024-6854?

5 open source packages ship an affected version, including h2o and ai.h2o:h2o-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `h2o` | PyPI | From 3.32.1.1 to 3.46.0 | None |
| `h2o` | PyPI | From 3.32.1.1 to 3.46.0 | None |
| `h2o` | PyPI | From 3.32.1.1 to 3.46.0 | None |
| `ai.h2o:h2o-core` | Maven | From 3.32.1.1 to 3.46.0 | None |
| `ai.h2o:h2o-core` | Maven | From 3.32.1.1 to 3.46.0 | None |

Products: H2o H2o.

## How do I fix CVE-2024-6854?

No fix has been published for CVE-2024-6854 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6854 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6854 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-6569](https://insights.sbomify.com/CVE-2023-6569/): External Control of File Name or Path in h2oai/h2o-3 (critical 9.3)
- [CVE-2023-6013](https://insights.sbomify.com/CVE-2023-6013/): H2O Local File Include (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6854 and fix it if it is affected.

What it is: CVE-2024-6854 is a high-severity path traversal vulnerability in h2oai/h2o-3, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6854 exists.

Affected packages and fixed versions:
- h2o (PyPI): affected from 3.32.1.1 up to 3.46.0; no fix listed
- h2o (PyPI): affected from 3.32.1.1 up to 3.46.0; no fix listed
- h2o (PyPI): affected from 3.32.1.1 up to 3.46.0; no fix listed
- ai.h2o:h2o-core (Maven): affected from 3.32.1.1 up to 3.46.0; no fix listed
- ai.h2o:h2o-core (Maven): affected from 3.32.1.1 up to 3.46.0; no fix listed

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-2024-6854/ (Markdown: https://insights.sbomify.com/CVE-2024-6854/index.md)
```

## Sources

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

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