Quick answers
- Is CVE-2026-45665 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45665 being exploited in the wild.
- How severe is CVE-2026-45665?
- High severity, with a CVSS score of 8.1, published 15 May 2026.
- Which products and versions are affected?
- open-webui (npm) SEMVER:introduced=0,fixed=0.8.0.
- Is there a fix for CVE-2026-45665?
- Yes. open-webui (npm): upgrade to 0.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45665 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45665?
- Check whether you run open-webui (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- open-webui (npm): upgrade to 0.8.0 or later
npm install open-webui@0.8.0
Technical details
A stored cross-site scripting (XSS) vulnerability exists in the Banner component of Open WebUI (specifically in `src/lib/components/common/Banner.svelte`). The root cause is an improper sanitization sequence where `DOMPurify.sanitize()` is called before the `marked` library parses the markdown. Because markdown link syntax like `[text](javascript:...)` is treated as plain text by DOMPurify, it passes through unsanitized; the `marked` library then converts it into an executable HTML anchor tag. An attacker with administrative privileges can use this to inject malicious JavaScript into global banners. When a Primary Admin (Super Admin) interacts with the banner, the script executes, potentially allowing the attacker to steal session tokens and escalate privileges. This is fixed in version 0.8.0 by reversing the order of operations.
Affected products
- Open WebUI open-webui <= 0.7.2
Identifiers
- CVE-2026-45665
- GHSA-cqp4-qqvg-3787
Timeline
- 2026-05-11: disclosed: Initial report by POV9en
- 2026-05-14: advisory: GitHub Advisory published
- 2026-05-14: patched: Fixed in version 0.8.0