Cross-Site Scripting (XSS) in open-webui (CVE-2026-45299)
Summary
Cross-site scripting in open-webui (CVE-2026-45299). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/users/{user_id}/profile/image. Mitigation: upgrade to >= 0.8.0 or later.
Original description
The description as published by the source.
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.8.0, the profile_image_url field on the user profile update form accepted arbitrary data: URI values without MIME-type validation, resulting in a XSS vulnerability. This vulnerability is fixed in 0.8.0.
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-45299 has been found in open-webui.
Attackers can target a specific entry point like GET /api/v1/users/{user_id}/profile/image over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade open-webui to >= 0.8.0 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-45299" on the vendor's site.
CVE-2026-45299 (open-webui) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: GET /api/v1/users/{user_id}/profile/image / profile_image_url / localStorage / validate_profile_image_url
Patched: >= 0.8.0 — 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.
Cross-site scripting (XSS) (CWE-79) exists in open-webui. Attackers reach the vulnerable code path via GET /api/v1/users/{user_id}/profile/image.
Check the vendor advisory for the affected versions of open-webui. Attack surface: GET /api/v1/users/{user_id}/profile/image / profile_image_url / localStorage / validate_profile_image_url.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to >= 0.8.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/users/{user_id}/profile/image requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/users/{user_id}/profile/image' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/users/{user_id}/profile/imageへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to >= 0.8.0ステージング環境で >= 0.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/users/{user_id}/profile/image on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com