Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-88001 medium CVSS 5.0

SSRF (Server-Side Request Forgery) in open-webui (CVE-2026-88001)

Summary

SSRF in open-webui (CVE-2026-88001). Risk of unauthorized operations or information disclosure. Exploitable via AIOHTTP_CLIENT_ALLOW_REDIRECTS. Mitigation: upgrade to 0.11.1 or later.

Original description

The description as published by the source.

Summary

Open WebUI protects server-side web fetches with two controls: the operator's list of excluded hosts, and a check that refuses private and internal addresses. Neither control was applied to the destination of an HTTP redirect. On a deployment where redirect following is enabled, any authenticated user who can cause the server to fetch a URL could submit a page that redirects, and the server would fetch the redirect destination without either control being applied to it. The server therefore connects to hosts the operator excluded, and to internal addresses including loopback, private networks and cloud metadata endpoints.

Preconditions

AIOHTTP_CLIENT_ALLOW_REDIRECTS must be set to true. Its default is false, and on the default the affected fetch paths do not follow redirects at all, so a deployment that has not changed this setting is not affected.

The attacker needs an authenticated account of any role, with access to any feature that causes the server to fetch a URL. Web search, ingesting a URL into a collection, the built-in page fetch tool and image URLs in chat all reach it. No internal hostnames need to be known, because the loopback and cloud metadata addresses are fixed and identical on every deployment.

Neither ENABLE_LOCAL_WEB_FETCH at its default of false nor any set of entries in WEB_FETCH_FILTER_LIST prevents this.

Impact

An authenticated user can make the server issue requests to hosts the operator deliberately excluded, and 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-88001 has been found in open-webui.
Attackers can target a specific entry point like AIOHTTP_CLIENT_ALLOW_REDIRECTS over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/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-88001" on the vendor's site.

CVE-2026-88001 (open-webui) — CWE-918 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: AIOHTTP_CLIENT_ALLOW_REDIRECTS / true / false / ENABLE_LOCAL_WEB_FETCH
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

SSRF (CWE-918) exists in open-webui. Attackers reach the vulnerable code path via AIOHTTP_CLIENT_ALLOW_REDIRECTS.

📍 Affected scope

Check the vendor advisory for the affected versions of open-webui. Attack surface: AIOHTTP_CLIENT_ALLOW_REDIRECTS / true / false / ENABLE_LOCAL_WEB_FETCH.

🔥 Severity

Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.

🔧 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"}]}]

References

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