Categories
CVE-2026-70480 medium CVSS 4.1

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

Summary

SSRF in open-webui (CVE-2026-70480). Risk of unauthorized operations or information disclosure. Exploitable via vega. Mitigation: upgrade to 5278eb906 or later.

Original description

The description as published by the source.

Summary

Open WebUI renders vega and vega-lite fenced code blocks in chat content by building a Vega view in the viewer's browser without a restricted resource loader. Any user who can place such a block where another user will see it can make that user's browser issue attacker-chosen outbound GET requests, and read back responses from same-origin or CORS-permissive targets into the rendered page. Because the request comes from the browser, server-side SSRF protections never see it.

Preconditions

Default configuration, no flags or environment variables involved: Vega blocks render unconditionally wherever chat content is displayed. The attacker needs an account that can put content in front of the victim, which covers a shared chat, a channel message, and model, RAG or tool output the attacker can influence. The victim must open the message, so this is not zero-click. Deployments where the victim's browser has no network position of interest lose little.

Impact

The victim's browser becomes a request proxy into whatever it can reach: internal hosts and ports behind the perimeter, same-site endpoints, and out-of-band beacons that confirm a chart was viewed and by whom. Where the target is same-origin or returns permissive CORS headers, the response body is pulled back into the chart in the victim's page, which turns the request into a read. Requests are GET only, and no server-side data is exposed to the attacker directly.

Fix

Fixed in 5278eb906 (#26806), rele…

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-70480 has been found in open-webui.
Attackers can target a specific entry point like vega over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.1/10.
What to do: upgrade open-webui to 5278eb906 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-70480" on the vendor's site.

CVE-2026-70480 (open-webui) — CWE-918 / CVSS v3 4.1
Attack vector: remote (network-reachable)
Attack surface: vega / load / sanitize / data.values
Patched: 5278eb906 — 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 vega.

📍 Affected scope

Check the vendor advisory for the affected versions of open-webui. Attack surface: vega / load / sanitize / data.values.

🔥 Severity

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

🔧 How to fix

Update to 5278eb906.

🛡️ 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 5278eb906

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

  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.0"}]}]
PyPI open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0.6.34"},{"fixed":"0.11.0"}]}]

References

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