Cyber Resilience

CVE-2026-45314

XSS in Openwebui Open Webui ≤ 0.9.3

Public PoCXSS
Published
15 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v4 7.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0022 13th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-45314 is a high-severity Improper Neutralization of Alternate XSS Syntax (CWE-87) vulnerability in Openwebui Open Webui. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as LLM Application Platforms; in the Other ATLAS/OWASP Terms risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.3, the channel webhook create/update flow accepts arbitrary profile_image_url values, including data:image/svg+xml;base64,... payloads. The profile image endpoint then decodes and serves this SVG as image/svg+xml…

more

without sanitization, allowing attacker-controlled script handlers (for example onload) to execute when the profile-image URL is opened in the browser. This vulnerability is fixed in 0.9.3.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: artificial intelligence, open webui

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-45346Same product: Openwebui Open Webui
CVE-2026-44549Same product: Openwebui Open Webui
CVE-2026-26193Same product: Openwebui Open Webui
CVE-2026-45299Same product: Openwebui Open Webui
CVE-2025-46571Same product: Openwebui Open Webui
CVE-2026-59214Same product: Openwebui Open Webui
CVE-2026-26192Same product: Openwebui Open Webui
CVE-2025-65959Same product: Openwebui Open Webui
CVE-2026-45665Same product: Openwebui Open Webui
CVE-2026-44721Same product: Openwebui Open Webui

Affected Assets

openwebui
open webui
≤ 0.9.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 requires developer testing and analysis that can discover improper neutralization of alternate script syntax after it has been coded.

SI-10 directly requires validation/sanitization of untrusted inputs, which structurally stops alternate XSS syntax from reaching the interpreter.

SA-8 mandates secure engineering principles such as input neutralization and output encoding that prevent introduction of this class of flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization and output encoding to prevent alternate XSS syntax.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require proper neutralization of alternate script syntax, directly eliminating CWE-87.

finds

Security testing catches residual XSS but does not itself implement the neutralization controls.

prevents

Secure SDLC mandates input validation and output encoding that directly prevent alternate XSS syntax.

prevents

Application security requirements explicitly call for neutralization of untrusted input to block XSS variants.

prevents

Secure architecture principles reduce attack surface but do not prescribe specific encoding rules.

References