CVE-2026-59213

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% 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, nvd
Elevated
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: 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.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.

CVSS v3
5.0
EG Score
5.0(medium)
EPSS
19.4%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (4)

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

Cross-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-5jqq
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

fix: 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/25783
github_commit

commit 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/0fc630b34b2899599dabffffa012afd47599aa75

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 23× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-13 22:31 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-12 23:33 UTCEG score recompute▲ 1.50
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-10 20:19 UTCNVD updateCVSS v3 → 5 · severity → MEDIUM
  22. 2026-07-09 17:18 UTCEG score recompute
  23. 2026-07-09 17:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59213?
CVE-2026-59213 is a medium vulnerability published on July 9, 2026. Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.27 before 0.10.0, getallmodels 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…
When was CVE-2026-59213 disclosed?
CVE-2026-59213 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-59213 actively exploited?
CVE-2026-59213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59213?
CVE-2026-59213 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-59213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59213, 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-59213

Explore →

Is Your Infrastructure Affected by CVE-2026-59213?

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

Start Free Scan →Browse All CVEs