Vulnerability in open-webui (CVE-2026-44569)
Summary
Vulnerability in open-webui (CVE-2026-44569). Data can be tampered with by attackers. Exploitable via message_id. Mitigation: upgrade to 0.6.19 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.6.19, there's an IDOR in the channels message management system that allows authenticated users to modify or delete any message within channels they have read access to. The vulnerability exists in the message update and delete endpoints, which implement channel-level authorization but completely lack message ownership validation. While the frontend correctly implements ownership checks (showing edit/delete buttons only for message owners or admins), the backend APIs bypass these protections by only validating channel access permissions without verifying that the requesting user owns the target message. This creates a client-side security control bypass where attackers can directly call the APIs to modify other users' messages. This vulnerability is fixed in 0.6.19.
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-44569 has been found in open-webui.
Attackers can target a specific entry point like message_id over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade open-webui to 0.6.19 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-44569" on the vendor's site.
CVE-2026-44569 (open-webui) — CWE-862 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: message_id
Patched: 0.6.19 — 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-862) exists in open-webui. Attackers reach the vulnerable code path via message_id.
Check the vendor advisory for the affected versions of open-webui. Attack surface: message_id.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 0.6.19.
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.19ステージング環境で 0.6.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com