Skip to content

← Actionable
Medium, CVSS 5.0amended

Open WebUI: Server-side fetches reach blocked and internal hosts via unvalidated HTTP redirect targets

CVE-2026-88001GHSA-5x7x-4c3c-qf5w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.11.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI open-webui

    Affected
    >= 0.9.5, <= 0.11.0
    Fixed in
    0.11.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
EPSS
  • CVE-2026-88001: 0.38% estimated exploitation activity in the next 30 days; percentile 31.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 AIOHTTPCLIENTALLOWREDIRECTS 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-5x7x-4c3c-qf5w

  2. Revision 2 · amended ·

    Amended from osv record GHSA-5x7x-4c3c-qf5w

  3. Revision 1 · created ·

    Published from ghsa record GHSA-5x7x-4c3c-qf5w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88001

Advisory: Open WebUI: Server-side fetches reach blocked and internal hosts via unvalidated HTTP redirect targets
IDs: CVE-2026-88001, GHSA-5x7x-4c3c-qf5w
Record: https://patchnext.com/advisories/cve-2026-88001 (revision 3, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: open-webui 0.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI open-webui: affected >= 0.9.5, <= 0.11.0; fixed in 0.11.1

## Suggested inspection (read-only)
- `python -m pip show open-webui`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on open-webui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5x7x-4c3c-qf5w (GitHub-reviewed advisory GHSA-5x7x-4c3c-qf5w lists affected ranges: PyPI open-webui >=0.9.5 <=0.11.0)
- Verified: https://osv.dev/vulnerability/GHSA-5x7x-4c3c-qf5w (OSV record GHSA-5x7x-4c3c-qf5w lists affected ranges: PyPI open-webui >=0.9.5 <0.11.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…