open-webui · Open WebUI · published 2026-08-04
CVE-2026-70492Open WebUI: Stored XSS via unescaped KaTeX render-error fallback in rendered messages
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-70492 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 35% of all CVEs. This Open WebUI vulnerability: CVSS 8.7 (v3.1). Fixed upstream in Open WebUI 0.11.0. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Open WebUI 0.11.0.
Patch events
AI toolingOpen WebUI
Open WebUI security release: 0.11.0
Upgrade to
0.11.0Why: CVE-2026-70492: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (35th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.7 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- open-webui open-webui
>= 0.10.0, < 0.11.0(affected)
Description (from the CVE record)#
Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.10.0 until 0.11.0, src/lib/components/chat/Messages/Markdown/KatexRenderer.svelte could store and render a chat message whose math block makes KaTeX fail with a stack overflow instead of a parse error. The catch branch fell back to inserting the original math source into the page as HTML through {@html} rather than as text, so script in the message runs in the browser of whoever views it, including shared chats and channels. The viewer's session token in localStorage can be stolen, and an administrator viewer can have their account taken over. This issue is fixed in 0.11.0.
Quoted from the CVE Program record.