Categories
CVE-2026-87014 medium CVSS 6.5

Vulnerability in open-webui (CVE-2026-87014)

Summary

Vulnerability in open-webui (CVE-2026-87014). Confidential information can be exposed externally. Exploitable via WEBUI_AUTH_TRUSTED_ROLE_HEADER. Mitigation: upgrade to 0.11.1 or later.

Original description

The description as published by the source.

Summary

A user who is demoted from admin by an identity provider keeps admin-level read and write access to every user's notes, over any Socket.IO connection that was already open when the demotion happened. Open WebUI caches the user's role on the socket at connection time, and the two SSO role-sync paths, the reverse-proxy trusted role header and OAuth role mapping, changed the role in the database without tearing that cached session down. Only the admin user-management endpoints invalidated sessions, so a demotion driven by the identity provider left the old privileges live on the socket.

Preconditions

A role-sync SSO mode has to be enabled. Either trusted-header authentication with WEBUI_AUTH_TRUSTED_ROLE_HEADER set, which is unset by default, or OAuth with role mapping enabled, which is off by default. Deployments that change roles only through the admin panel are not affected, because that path already invalidated the user's sockets.

The account has to be an admin at the moment it opens a Socket.IO connection, has to keep that connection open across the demotion, and has to be demoted through the SSO path rather than through the admin panel. Signing out, reloading the page, or any network interruption ends the exposure, because the reconnect reads a fresh role from the database.

Impact

Until the socket closes, the demoted account can open and edit any user's note through the collaborative-notes socket handlers, which grant admins access to every note. T…

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-87014 has been found in open-webui.
Attackers can target a specific entry point like WEBUI_AUTH_TRUSTED_ROLE_HEADER over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade open-webui to 0.11.1 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-87014" on the vendor's site.

CVE-2026-87014 (open-webui) — CWE-613 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: WEBUI_AUTH_TRUSTED_ROLE_HEADER / ce3c175e260709f359d7e6cbb3132f0572098b95 / user
Patched: 0.11.1 — 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

A vulnerability (CWE-613) exists in open-webui. Attackers reach the vulnerable code path via WEBUI_AUTH_TRUSTED_ROLE_HEADER.

📍 Affected scope

Check the vendor advisory for the affected versions of open-webui. Attack surface: WEBUI_AUTH_TRUSTED_ROLE_HEADER / ce3c175e260709f359d7e6cbb3132f0572098b95 / user.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.11.1.

🛡️ 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 request patterns matching this CVE's known IOCs. 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

  1. 1
    Identify exposure identify
    grep -r 'open-webui' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で open-webui を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade open-webui to 0.11.1

    ステージング環境で 0.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.1"}]}]
PyPI open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0.9.0"},{"fixed":"0.11.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details