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 78% 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.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: Elevated riskExposed: 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)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
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

Vendor Advisories for CVE-2026-59213(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
open-webui0.6.27 ... 0.9.6 (40 versions)0.10.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 52× 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-08-25 14:47 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 12:53 UTCEG score recompute
  4. 2026-08-23 11:16 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 09:39 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 08:01 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 06:24 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 04:39 UTCEG score recompute
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-18 02:54 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 00:24 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 22:47 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 21:09 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 17:55 UTCEG score recompute
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 16:19 UTCEG score recompute
Show 60 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-10 14:41 UTCEG score recompute
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-09 13:04 UTCEG score recompute
  5. 2026-08-08 16:37 UTCEPSS rescore
  6. 2026-08-08 11:27 UTCEG score recompute
  7. 2026-08-07 09:50 UTCEG score recompute
  8. 2026-08-06 13:47 UTCEPSS rescore
  9. 2026-08-06 08:13 UTCEG score recompute
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 06:37 UTCEG score recompute
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 10:39 UTCEPSS rescore
  14. 2026-08-04 04:25 UTCEG score recompute
  15. 2026-08-03 10:36 UTCEPSS rescore
  16. 2026-08-03 02:48 UTCEG score recompute
  17. 2026-08-02 02:27 UTCEPSS rescore
  18. 2026-08-02 01:11 UTCEG score recompute
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-30 21:50 UTCEG score recompute
  21. 2026-07-30 16:28 UTCEPSS rescore
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-28 17:15 UTCEG score recompute
  25. 2026-07-28 15:37 UTCEPSS rescore
  26. 2026-07-27 15:35 UTCEG score recompute
  27. 2026-07-27 14:14 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 12:18 UTCEG score recompute
  31. 2026-07-25 14:18 UTCEPSS rescore
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-24 14:18 UTCEPSS rescore
  34. 2026-07-24 14:18 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 03:21 UTCEG score recompute
  38. 2026-07-22 14:08 UTCEPSS rescore
  39. 2026-07-22 14:08 UTCEPSS rescore
  40. 2026-07-21 15:25 UTCEPSS rescore
  41. 2026-07-21 15:25 UTCEPSS rescore
  42. 2026-07-20 17:08 UTCEPSS rescore
  43. 2026-07-19 14:31 UTCEPSS rescore
  44. 2026-07-19 02:29 UTCEPSS rescore
  45. 2026-07-18 10:04 UTCEPSS rescore
  46. 2026-07-16 17:03 UTCEPSS rescore
  47. 2026-07-15 16:57 UTCEPSS rescore
  48. 2026-07-15 16:57 UTCEPSS rescore
  49. 2026-07-15 02:00 UTCEPSS rescore
  50. 2026-07-15 02:00 UTCEPSS rescore
  51. 2026-07-13 22:31 UTCEPSS rescore
  52. 2026-07-13 06:13 UTCEPSS rescore
  53. 2026-07-13 06:13 UTCEPSS rescore
  54. 2026-07-12 23:33 UTCEG score recompute▲ 1.50
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-10 20:19 UTCNVD updateCVSS v3 → 5 · severity → MEDIUM
  59. 2026-07-09 17:18 UTCEG score recompute
  60. 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 0% probability of exploitation in the next 30 days, which ranks it in the top 78.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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