Quick answers
- Is CVE-2025-65959 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-65959 being exploited in the wild.
- How severe is CVE-2025-65959?
- High severity, with a CVSS score of 8.7, published 4 December 2025.
- Which products and versions are affected?
- open-webui (npm) SEMVER:introduced=0,fixed=0.6.37.
- Is there a fix for CVE-2025-65959?
- Yes. open-webui (npm): upgrade to 0.6.37 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-65959 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-65959?
- Check whether you run open-webui (npm) or Openwebui Open Webui 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.6.37 or later
npm install open-webui@0.6.37
Technical details
This is a stored DOM-based cross-site scripting (XSS) vulnerability in the Notes feature's PDF download functionality. The vulnerable code in src/lib/components/notes/utils.ts directly assigns user-controlled HTML content to innerHTML without sanitization or validation, allowing malicious SVG or script tags to be stored and later executed. An authenticated attacker can import a specially crafted Markdown file containing SVG payloads with event handlers (e.g., onload="navigator.sendBeacon()"), and when a victim downloads the note as PDF, the JavaScript executes in the victim's browser context with access to localStorage tokens. The root cause is incomplete TipTap editor configuration that does not block dangerous tags and missing DOMPurify sanitization during PDF generation. A patch is available in version 0.6.37 that sanitizes HTML output using DOMPurify with a strict allowlist.
Affected products
- Open WebUI Open WebUI <= 0.6.36
Identifiers
- CVE-2025-65959
- GHSA-8wvc-869r-xfqf
Timeline
- 2025-12-04: disclosed
- 2025-12-04: patched: Fixed in version 0.6.37