# CVE-2026-65700: h2oGPT 0.2.1 Path Traversal via OpenAI-compatible Files API

> Unauthenticated attackers can achieve remote code execution and arbitrary file access in h2oGPT via path traversal in the OpenAI-compatible Files API.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-ffpm-9hgc-84cg

## What is CVE-2026-65700?

CVE-2026-65700 is a critical path traversal vulnerability in h2oai h2ogpt, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

h2oGPT through 0.2.1 contains a path traversal vulnerability in the OpenAI-compatible files API that allows unauthenticated remote attackers to read, write, and delete arbitrary files accessible to the server process by supplying traversal sequences in the bearer token. The get_user_dir function in openai_server/backend_utils.py uses the bearer token string unsanitized as a path component via os.path.join, and because the default API key is EMPTY authentication is bypassed, enabling attackers to traverse outside the intended user directory through the file content, delete, and upload endpoints to achieve remote code execution by writing to startup hooks or application-loaded files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-65700?


## How do I fix CVE-2026-65700?

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

## Is CVE-2026-65700 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65700 and fix it if it is affected.

What it is: CVE-2026-65700 is a critical path traversal vulnerability in h2oai h2ogpt, published on 23 Jul 2026. 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-2026-65700 exists.

Affected product: h2oai h2ogpt. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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