AI Threat Alert
Open-Webui
AI Threat Alert tracks 34 known AI/ML vulnerabilities affecting Open-Webui products — each enriched with CVSS severity, EPSS exploit probability, patch status, and CISO-grade analysis. Browse every Open-Webui CVE below, sorted by severity and recency.
| Severity | CVE | Headline | Package | CVSS |
|---|---|---|---|---|
| MEDIUM | CVE-2026-87014 | Open WebUI: demoted admins keep socket access to all notes | open-webui | 6.5 |
| MEDIUM | CVE-2026-87013 | Open WebUI: authenticated DoS via folder cycle | open-webui | 4.3 |
| MEDIUM | CVE-2026-87012 | Open WebUI: type confusion suppresses all reminders | open-webui | 4.3 |
| HIGH | CVE-2026-87011 | Open WebUI: unauth DoS via OIDC logout handler | open-webui | 7.5 |
| MEDIUM | CVE-2026-87015 | Open WebUI: session cookies leak to rogue tool server | open-webui | 6.8 |
| MEDIUM | CVE-2026-87017 | Open WebUI: KB metadata leaks across tenants in 11 backends | open-webui | 4.3 |
| HIGH | CVE-2026-87996 | Open WebUI: DNS rebinding SSRF exposes internal svcs | open-webui | 7.7 |
| HIGH | CVE-2026-87995 | Open WebUI: XSS in terminal preview hijacks user accounts | open-webui | 8.7 |
| HIGH | CVE-2026-87016 | Open WebUI: OAuth wildcard bug hijacks admin sessions | open-webui | 8.1 |
| MEDIUM | CVE-2026-87994 | Open WebUI: channel authz gap allows message spoofing | open-webui | 4.3 |
| MEDIUM | CVE-2026-87997 | Open WebUI: folder auth bypass injects rogue chats | open-webui | 4.3 |
| HIGH | CVE-2026-87999 | Open WebUI: SSRF leaks Azure platform channel | open-webui | 7.1 |
| HIGH | CVE-2026-87998 | Open WebUI: authZ flaw lets users kill shared KB configs | open-webui | 7.1 |
| MEDIUM | CVE-2026-88006 | Open WebUI: OAuth endpoint skips role revocation checks | open-webui | 6.5 |
Page 2 of 2
Frequently asked questions
How many known vulnerabilities affect Open-Webui?
34 AI/ML CVEs affecting Open-Webui products are tracked, sourced from NVD and GitHub Advisory.
What Open-Webui products are affected?
The CVEs below map to the Open-Webui AI/ML packages and tools tracked by AI Threat Alert; open any CVE to see the affected components and versions.
Where does the Open-Webui vulnerability data come from?
Data is sourced from NVD and GitHub Advisory, then enriched with CVSS severity, EPSS exploit probability, and patch status for each CVE.
How can I monitor Open-Webui for new vulnerabilities?
AI Threat Alert tracks Open-Webui continuously; a Pro subscription adds breaking alerts when new CVEs affecting Open-Webui are published.
How do I assess Open-Webui's security exposure?
Each CVE below carries CVSS severity and exploitation signals, so you can review the highest-severity Open-Webui issues first and judge the exposure for your stack.