Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.27 before 0.10.0, get_all_models handlers in routers/openai.py and routers/ollama.py passed a lambda to aiocache key instead of key_builder, causing permission-filtered per-user model lists to share a static cache entry and exposing one user’s model list to another caller during the TTL window. This issue is fixed in version 0.10.0.
CVE-2026-59213
This low-severity CVE scores 3.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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
- 5.0
- EG Score
- 3.5(low)
- EPSS
- 17.1%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026Cross-user model-list exposure via static cache key in get_all_models (aiocache key= vs key_builder= misuse) · Advisory · open-webui/open-webui · GitHub
https://github.com/open-webui/open-webui/security/advisories/GHSA-3wp3-xxj9-5jqqv0.10.0
Patch available: open-webui/open-webui v0.10.0
https://github.com/open-webui/open-webui/releases/tag/v0.10.0fix: per-user model cache used static key= (cross-user model exposure)
Fix merged in open-webui/open-webui PR #25783 on 2026-06-29 — awaiting tagged release
https://github.com/open-webui/open-webui/pull/25783commit 0fc630b34b28 (open-webui/open-webui)
Fix landed in open-webui/open-webui commit 0fc630b34b28 — awaiting tagged release
https://github.com/open-webui/open-webui/commit/0fc630b34b2899599dabffffa012afd47599aa75Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 20:19 UTCNVD updateCVSS v3 → 5 · severity → MEDIUM
- 2026-07-09 17:18 UTCEG score recompute
- 2026-07-09 17:15 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59213?
When was CVE-2026-59213 disclosed?
Is CVE-2026-59213 actively exploited?
What is the CVSS score of CVE-2026-59213?
How do I remediate CVE-2026-59213?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59213
Is Your Infrastructure Affected by CVE-2026-59213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.