CVE-2026-59219

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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.0 before 0.10.0 with Redis configured, Socket.IO connect, user-join, join-channels, join-note, and the terminal websocket first-message authentication used decode_token without the Redis-backed is_valid_token revocation check, allowing revoked JWTs to continue authenticating realtime connections. This issue is fixed in version 0.10.0.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
17.2%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Realtime endpoints accept Redis-revoked JWTs after signout/backchannel logout · Advisory · open-webui/open-webui · GitHub

https://github.com/open-webui/open-webui/security/advisories/GHSA-855v-hq7w-jmjw
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_commit

commit 33b91bd8ae8a (open-webui/open-webui)

Fix landed in open-webui/open-webui commit 33b91bd8ae8a — awaiting tagged release

https://github.com/open-webui/open-webui/commit/33b91bd8ae8a100a5a306c91441a7d0b422c4cde

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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-12 10:18 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 23:28 UTCEG score recompute
  4. 2026-07-11 12:39 UTCEG score recompute
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 01:49 UTCEG score recompute
  8. 2026-07-10 14:59 UTCEG score recompute
  9. 2026-07-10 04:09 UTCEG score recompute
  10. 2026-07-09 17:18 UTCEG score recompute
  11. 2026-07-09 17:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59219?
CVE-2026-59219 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.0 before 0.10.0 with Redis configured, Socket.IO connect, user-join, join-channels, join-note, and the terminal websocket first-message authentication used decodetoken without the Redis-backed…
When was CVE-2026-59219 disclosed?
CVE-2026-59219 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-59219 actively exploited?
CVE-2026-59219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59219?
CVE-2026-59219 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-59219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59219, 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-59219

Explore →

Is Your Infrastructure Affected by CVE-2026-59219?

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