← Back
CVE-2025-64495
Cross-Site Scripting (XSS) in open-webui (CVE-2025-64495)
Summary
cross-site scripting in open-webui (CVE-2025-64495). Confidential information can be exposed externally. Exploitable via ``tempDiv.innerHTML``. Mitigation: upgrade to `0.6.35` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-64495** has been found in open-webui.
Attackers can target a specific entry point like ``tempDiv.innerHTML`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade open-webui to **0.6.35** or later.
If unsure, ask your IT team or search "open-webui CVE-2025-64495" on the vendor's site.
CVE-2025-64495 (open-webui) — CWE-79 /
Attack vector: remote (network-reachable)
Attack surface: `tempDiv.innerHTML` / `marked.parse` / `String.fromCodePoint`
Patched: `0.6.35` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in open-webui. Attackers reach the vulnerable code path via ``tempDiv.innerHTML`` without authentication.
📍 Affected scope
open-webui — . Attack surface: `tempDiv.innerHTML` / `marked.parse` / `String.fromCodePoint`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.6.35**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'open-webui' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'open-webui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `open-webui` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade open-webui to 0.6.35ステージング環境で 0.6.35 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.6.35"}]}]
npm
open-webui
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.6.35"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-64495
- advisory https://github.com/advisories/GHSA-w7xj-8fx7-wfch
- package https://github.com/open-webui/open-webui
- package https://pypi.org/project/open-webui
- web https://github.com/open-webui/open-webui/security/advisories/GHSA-w7xj-8fx7-wfch
- web https://github.com/open-webui/open-webui/commit/eb9c4c0e358c274aea35f21c2856c0a20051e5f1
- web https://github.com/open-webui/open-webui/blob/7a83e7dfa367d19f762ec17cac5e4a94ea2bd97d/src/lib/components/common/RichTextInput.svelte#L348