CVE-2026-65700
Unauthenticated path traversal in h2oGPT files API allows remote code execution.
Is CVE-2026-65700 being exploited?
Not confirmed. CVE-2026-65700 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.5% probability of exploitation in the next 30 days.
How severe is CVE-2026-65700?
CVE-2026-65700 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65700?
Not known from our data. No patch reference has been recorded for CVE-2026-65700, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-65700 affect?
CVE-2026-65700 affects h2oGPT <= 0.2.1, h2oGPT OpenAI-compatible files API, Self-hosted h2oGPT deployments using default EMPTY API key. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65700?
Disable files API, enforce API keys, restrict filesystem permissions, and apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can read, write, delete server files via bearer-token path traversal, enabling RCE by writing startup hooks or application-loaded files.
Immediate action required
- affected<= 0.2.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.