CVE-2026-65700
h2oGPT versions up to 0.2.1 have a path‑traversal flaw in the OpenAI‑compatible files API. By sending traversal sequences in the bearer token, an unauthenticated attacker can read, write, or delete any file the server can access. This can lead to remote code execution if the attacker writes malicious code to startup hooks or other application files.
No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.
Who is affected
h2oGPT 0.2.1 and earlier releases that expose the OpenAI‑compatible files API with the default empty API key.
Real-world impact
An attacker could read sensitive files, modify or delete critical configuration files, or inject executable code that the server will run, effectively taking control of the host.
Why this severity
The CVSS score of 9.3 reflects the vulnerability’s high impact on confidentiality, integrity, and availability, combined with low attack complexity, no authentication required, and no user interaction needed.
What to do about it
- ›Set a non‑empty API key to enforce authentication for the files API.
- ›Disable or restrict access to the OpenAI‑compatible files API endpoints until a patch is released.
No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.
No fix documented in sources
Timeline
- Jul 23, 2026 · 9d agoPublishedDisclosed and added to the National Vulnerability Database.
- Jul 27, 2026 · 5d agoAdvisory updatedThe NVD record was last revised.