CVE-2026-59221

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.6 before 0.10.0, _sanitize_proxy_path in backend/open_webui/routers/terminals.py decoded proxy paths only eight times, allowing a nine-times percent-encoded ../ traversal value to pass normalization checks and be decoded by the upstream terminal server. This issue is fixed in version 0.10.0.

CVSS v3
7.7
EG Score
7.7(medium)
EPSS
28.3%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Jul 9, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available

open-webui terminal proxy path traversal guard bypass via 9x encoded traversal · Advisory · open-webui/open-webui · GitHub

https://github.com/open-webui/open-webui/security/advisories/GHSA-frvj-c5qp-xj4w
github_release Patch Available

v0.10.0

Patch available: open-webui/open-webui v0.10.0

https://github.com/open-webui/open-webui/releases/tag/v0.10.0
github_pr

Fail closed when the proxy/redirect path decode cap is exceeded

Fix merged in open-webui/open-webui PR #26050 on 2026-06-16 — awaiting tagged release

https://github.com/open-webui/open-webui/pull/26050
github_commit

commit 05098d25a58d (open-webui/open-webui)

Fix landed in open-webui/open-webui commit 05098d25a58d — awaiting tagged release

https://github.com/open-webui/open-webui/commit/05098d25a58d03738e01c4e85e8852c3b4ad849c

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 23:37 UTCEG score recompute
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 10:54 UTCEG score recompute
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 22:12 UTCEG score recompute
  7. 2026-07-12 09:29 UTCEG score recompute
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 20:47 UTCEG score recompute
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:05 UTCEG score recompute
  13. 2026-07-10 19:23 UTCEG score recompute
  14. 2026-07-10 06:41 UTCEG score recompute
  15. 2026-07-09 17:57 UTCEG score recompute
  16. 2026-07-09 17:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59221?
CVE-2026-59221 is a high vulnerability published on July 9, 2026. Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.6 before 0.10.0, sanitizeproxypath in backend/openwebui/routers/terminals.py decoded proxy paths only eight times, allowing a nine-times percent-encoded ../ traversal value to pass normalization checks…
When was CVE-2026-59221 disclosed?
CVE-2026-59221 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59221 actively exploited?
CVE-2026-59221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59221?
CVE-2026-59221 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-59221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59221, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59221

Explore →

Is Your Infrastructure Affected by CVE-2026-59221?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.