Vulnerability in open-webui (CVE-2026-45346)
Summary
Vulnerability in open-webui (CVE-2026-45346). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.6.31 or later.
Original description
The description as published by the source.
Summary
There is a Cross-Site Scripting vulnerability in Open WebUI SVG renderer implementation.
Details
It is possible permanently save any HTML/JavaScript code in the application, which can be then executed in the context of the application domain. This behaviour can be used to extract and steal sensitive data from the application, manipulate DOM tree or being used in complex client-side attacks.
Detailed step-by-step instruction provided below. Please keep me updated about assigned CVE identifier. I'd like to be credited as: Jakub Żoczek [Securitum]
PoC
Steps to reproduce:
To reproduce this vulnerability you need to:
- Login to Open WebUI
- Start new conversation / thread
- Use prompt: "Hey. Can you draw me a green circle using SVG ?"
- SVG image should be generated.
- Now it's possible to edit the code by simply clicking on it and adding additional code. Add payload ``
- The whole code should look like this:
ok
- Now clicking "Save", the new image should get rendered, and malicious code - executed (by popping alert).
Such thread could be then shared and sent to other users.
Impact
Cross-Site Scripting allows attacker to execute malicious code in context of victim's browser. This way it could be used in malicious client-side attack achieving different things, depends on attacker's goal. Such thread with rendered SVG could be shared to other user (or administrator) and gain sensitive data…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45346 has been found in open-webui.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade open-webui to 0.6.31 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-45346" on the vendor's site.
CVE-2026-45346 (open-webui) — CWE-80 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 0.6.31 — 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.
A vulnerability (CWE-80) exists in open-webui.
Check the vendor advisory for the affected versions of open-webui.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.6.31.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade open-webui to 0.6.31ステージング環境で 0.6.31 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com