Vulnerability in open-webui (CVE-2026-59215)
Summary
Vulnerability in open-webui (CVE-2026-59215). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/channels/{id}/messages/{message_id}/thread. Mitigation: upgrade to 0.10.0 or later.
Original description
The description as published by the source.
Summary
A normal authenticated user can read the content of a message in a private channel they do not belong to. GET /api/v1/channels/{id}/messages/{message_id}/thread authorizes the caller against the URL channel, but the underlying thread lookup loads the thread parent by id and returns it without verifying the parent belongs to that channel. By requesting a thread in a channel they can access while supplying a victim channel's message id as the thread root, the attacker receives the victim message — content, channel id, and author.
Affected component
backend/open_webui/models/messages.py—get_messages_by_parent_id()backend/open_webui/routers/channels.py—get_channel_thread_messages()(read),new_message_handler()(parent/reply binding on write)
Root cause
get_messages_by_parent_id(channel_id, parent_id) filters the thread replies by channel_id, but loads the thread parent by id alone and appends it without requiring parent.channel_id == channel_id:
message = await db.get(Message, parent_id) # loaded by id only — no channel binding
if not message:
return []
# replies are filtered by channel_id ...
if len(all_messages) < limit:
all_messages.append(message) # parent appended unconditionally
get_channel_thread_messages() authorizes only the URL channel, then calls get_messages_by_parent_id(id, message_id) with the caller-supplied message_id. The reply insert path (`new_message_handler…
Source: NIST National Vulnerability Database 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-59215 has been found in open-webui.
Attackers can target a specific entry point like GET /api/v1/channels/{id}/messages/{message_id}/thread over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade open-webui to 0.10.0 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-59215" on the vendor's site.
CVE-2026-59215 (open-webui) — CWE-639 / CVSS v3 3.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/channels/{id}/messages/{message_id}/thread / GET /channels/{attacker_channel}/messages/{victim_message_id}/thread / channel_id / message_id
Patched: 0.10.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-639) exists in open-webui. Attackers reach the vulnerable code path via GET /api/v1/channels/{id}/messages/{message_id}/thread.
Check the vendor advisory for the affected versions of open-webui. Attack surface: GET /api/v1/channels/{id}/messages/{message_id}/thread / GET /channels/{attacker_channel}/messages/{victim_message_id}/thread / channel_id / message_id.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 0.10.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/channels/{id}/messages/{message_id}/thread 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/channels/{id}/messages/{message_id}/thread' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/channels/{id}/messages/{message_id}/threadへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.10.0ステージング環境で 0.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/channels/{id}/messages/{message_id}/thread on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com