Vulnerability in open-webui (CVE-2026-44571)
Summary
Vulnerability in open-webui (CVE-2026-44571). Data can be tampered with by attackers. Exploitable via POST /api/v1/channels/{channel_id}/messages/{message_id}/update. Mitigation: upgrade to 0.8.6 or later.
Original description
The description as published by the source.
Vulnerability Description
In standard channels (i.e., channels whose channel.type is neither group nor dm), the endpoint
POST /api/v1/channels/{channel_id}/messages/{message_id}/update can be accessed with read permission only.
When access_control is set to None, the authorization check has_access(..., type="read") evaluates to True, allowing users who are not the message owner to update messages.
As a result, unauthorized modification of other users’ messages is possible.
Attack Prerequisites
- The attacker is an authenticated user (role
useror higher) - The target channel is a standard channel (i.e., not
groupordm) access_controlisNoneor allowsreadaccess- The attacker can obtain the target
message_id(e.g., via the channel’s message list)
Attack Scenario
-
The attacker (User B) retrieves another user’s
message_idfrom the message list in a standard channel -
The attacker sends a request to
POST /api/v1/channels/{channel_id}/messages/{message_id}/update -
The message authored by another user (User A) is successfully updated
Potential Impact
- Unauthorized modification of other users’ messages (violation of data integrity)
Steps to Reproduce
-
Log in as an administrator
-
Create User A
-
Create User B
-
Log in as User A
-
Log in as User B
-
As the administrator, create a new channel
-
As User A, post a new message in the channel
-
As User B, edit User A’s messag…
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-44571 has been found in open-webui.
Attackers can target a specific entry point like POST /api/v1/channels/{channel_id}/messages/{message_id}/update over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade open-webui to 0.8.6 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-44571" on the vendor's site.
CVE-2026-44571 (open-webui) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/channels/{channel_id}/messages/{message_id}/update / channel.type / group / access_control
Patched: 0.8.6 — 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 POST /api/v1/channels/{channel_id}/messages/{message_id}/update.
Check the vendor advisory for the affected versions of open-webui. Attack surface: POST /api/v1/channels/{channel_id}/messages/{message_id}/update / channel.type / group / access_control.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 0.8.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/channels/{channel_id}/messages/{message_id}/update 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 'POST /api/v1/channels/{channel_id}/messages/{message_id}/update' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/channels/{channel_id}/messages/{message_id}/updateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.8.6ステージング環境で 0.8.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/channels/{channel_id}/messages/{message_id}/update on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com