Vulnerability in open-webui (CVE-2026-44553)
Summary
Vulnerability in open-webui (CVE-2026-44553). Confidential information can be exposed externally. Exploitable via POST /api/v1/users/{B_id}/update. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Stale Admin Role in Socket.IO Session Pool Enables Post-Demotion Cross-User Note Access
Affected Component
Socket.IO session state and role-check callsites:
backend/open_webui/socket/main.py(lines 330-351,connecthandler — role snapshotted into SESSION_POOL)backend/open_webui/socket/main.py(lines 393-398,heartbeathandler — does not refresh role)backend/open_webui/socket/main.py(line 538,ydoc:document:join— uses cached role for admin check)backend/open_webui/socket/main.py(line 611,document_save_handler— uses cached role for admin check)backend/open_webui/routers/users.py(lines 557-633, role update — does not invalidate SESSION_POOL)backend/open_webui/routers/users.py(line 641, user delete — does not invalidate SESSION_POOL)
Affected Versions
Current main branch (commit 6fdd19bf1) and likely all versions with the collaborative document (Yjs) Socket.IO handlers.
Description
When a user connects via Socket.IO, the connect handler authenticates them via JWT and stores their user record (including role) in the in-memory SESSION_POOL dictionary keyed by session ID. The heartbeat handler keeps the session alive indefinitely but only refreshes the last_seen_at timestamp — never the role.
Role checks in the Yjs collaborative document handlers (ydoc:document:join, document_save_handler) consult the cached SESSION_POOL role rather than the database. Meanwhile, administrative role changes and user delet…
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-44553 has been found in open-webui.
Attackers can target a specific entry point like POST /api/v1/users/{B_id}/update over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/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-44553" on the vendor's site.
CVE-2026-44553 (open-webui) — CWE-384 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/users/{B_id}/update / connect / heartbeat / document_save_handler
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.
A vulnerability (CWE-384) exists in open-webui. Attackers reach the vulnerable code path via POST /api/v1/users/{B_id}/update.
Check the vendor advisory for the affected versions of open-webui. Attack surface: POST /api/v1/users/{B_id}/update / connect / heartbeat / document_save_handler.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.9.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/users/{B_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/users/{B_id}/update' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/users/{B_id}/updateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade open-webui to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/users/{B_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