← Back
CVE-2026-44558
Authorization Flaw in open-webui (CVE-2026-44558)
Summary
vulnerability in open-webui (CVE-2026-44558). Risk of unauthorized operations or information disclosure. Exploitable via `POST /api/v1/channels/`. Mitigation: upgrade to `0.9.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44558** has been found in open-webui.
Attackers can target a specific entry point like `POST /api/v1/channels/` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade open-webui to **0.9.0** or later.
If unsure, ask your IT team or search "open-webui CVE-2026-44558" on the vendor's site.
CVE-2026-44558 (open-webui) — CWE-863 /
Attack surface: POST /api/v1/channels/ / POST /api/v1/channels/{id}/update / `create_new_channel` / `update_channel_by_id`
Patched: `0.9.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.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in open-webui. Attackers reach the vulnerable code path via `POST /api/v1/channels/` without authentication.
📍 Affected scope
open-webui — . Attack surface: POST /api/v1/channels/ / POST /api/v1/channels/{id}/update / `create_new_channel` / `update_channel_by_id`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.9.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /api/v1/channels/` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/v1/channels/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/v1/channels/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade open-webui to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/v1/channels/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.0"}]}]