Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.10.0, WEB_FETCH_FILTER_LIST matching compared configured host entries against URL strings and non-label-boundary suffixes, allowing path-based blocklist bypasses such as !internal.example.com in a URL path and sibling-domain matches that did not reflect the intended hostname policy. This issue is fixed in version 0.10.0.
CVE-2026-59223
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EPSS
- 12.9%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 9, 2026`WEB_FETCH_FILTER_LIST` host allow/block filter bypassable via URL path and non-label-boundary matching · Advisory · open-webui/open-webui · GitHub
https://github.com/open-webui/open-webui/security/advisories/GHSA-qg3f-8x3j-ggf2v0.10.0
Patch available: open-webui/open-webui v0.10.0
https://github.com/open-webui/open-webui/releases/tag/v0.10.0Match WEB_FETCH_FILTER_LIST on hostnames with label boundaries, not URL suffix
Fix merged in open-webui/open-webui PR #25949 on 2026-06-16 — awaiting tagged release
https://github.com/open-webui/open-webui/pull/25949commit 087878ce848a (open-webui/open-webui)
Fix landed in open-webui/open-webui commit 087878ce848a — awaiting tagged release
https://github.com/open-webui/open-webui/commit/087878ce848a4d828012068b5997dac480f43656Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 14:34 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 15:56 UTCEG score recompute
- 2026-07-09 17:17 UTCEG score recompute
- 2026-07-09 17:15 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS 91%CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS 99%CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8MEDIUM
- CVE-2020-10887EG 9.8EPSS 90%CRITICAL
- CVE-2017-3197EG 9.8EPSS 92%CRITICAL
- CVE-2018-9318EG 9.8EPSS 90%CRITICAL
- CVE-2018-9311EG 9.8CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2022-22759EG 9.6CRITICAL
Frequently asked(5)
What is CVE-2026-59223?
When was CVE-2026-59223 disclosed?
Is CVE-2026-59223 actively exploited?
What is the CVSS score of CVE-2026-59223?
How do I remediate CVE-2026-59223?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59223
Is Your Infrastructure Affected by CVE-2026-59223?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.