Vulnerability in open-webui (CVE-2026-70481)
Summary
Vulnerability in open-webui (CVE-2026-70481). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1/channels/{id}/messages/{message_id}/update. Mitigation: upgrade to 0.11.0 or later.
Original description
The description as published by the source.
Summary
On standard channels, the message update and delete handlers accepted any caller holding write access on the channel, without checking that the caller wrote the message. Write access is the same grant a member needs in order to post, so every ordinary participant in a shared channel could rewrite or permanently delete any other participant's messages. The group and direct message branch of the same handlers enforced authorship; the standard branch did not.
Preconditions
Channels are disabled by default and must be enabled by an administrator (ENABLE_CHANNELS). The channel must be a standard channel; group and direct message channels are not affected. The attacker is any authenticated account with role user that holds write access on the channel, whether granted publicly, per user, or through a group. No ownership of the channel, channel manager role, or elevated role is required. Channel and message ids are returned by the listing endpoints the member can already call.
Impact
An ordinary member could replace the content of another member's message while the message stayed attributed to its original author, and could attach arbitrary data and meta payloads to it through the same form. The member could also permanently delete other members' messages, up to the entire visible history of the channel. This is an integrity and availability loss against other users of the channel: content can be forged under a colleague's name and records can be destroyed.…
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-70481 has been found in open-webui.
Attackers can target a specific entry point like POST /api/v1/channels/{id}/messages/{message_id}/update 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.11.0 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-70481" on the vendor's site.
CVE-2026-70481 (open-webui) — CWE-284 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/channels/{id}/messages/{message_id}/update / DELETE /api/v1/channels/{id}/messages/{message_id}/delete / ENABLE_CHANNELS / user
Patched: 0.11.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.
A vulnerability (CWE-284) exists in open-webui. Attackers reach the vulnerable code path via POST /api/v1/channels/{id}/messages/{message_id}/update.
Check the vendor advisory for the affected versions of open-webui. Attack surface: POST /api/v1/channels/{id}/messages/{message_id}/update / DELETE /api/v1/channels/{id}/messages/{message_id}/delete / ENABLE_CHANNELS / user.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.11.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 POST /api/v1/channels/{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/{id}/messages/{message_id}/update' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/channels/{id}/messages/{message_id}/updateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.11.0ステージング環境で 0.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/channels/{id}/messages/{message_id}/update on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com