Skip to content

← Actionable
Medium, CVSS 4.3amended

Open WebUI: Any authenticated user can start a non-terminating request via a folder parent cycle

CVE-2026-87013GHSA-8r35-5x5r-hv74

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.10.0, <= 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
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2026-87013: 0.48% estimated exploitation activity in the next 30 days; percentile 41.78 (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 Any authenticated user can move one of their own folders under itself, leaving a loop in their folder tree. The re-parent endpoint performed no check that the new parent was not the folder itself or one of its own subfolders, and the folder tree walks did not track which folders they had already visited. A single request against a folder in a loop therefore never finishes. Preconditions Folders must be enabled (ENABLEFOLDERS, default true) and the acting user's role must hold the folders feature permission (USERPERMISSIONSFEATURESFOLDERS, default true). Both are on in a default install. Any authenticated account is sufficient: no administrator, no second user, no shared folder and no victim interaction. Deployments that disable folders, or withhold the folders feature permission from non-admin roles, are not affected. Impact A single request that never returns. It keeps running after the client disconnects, holds a CPU core and grows its in-memory folder list at roughly 0.6…

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

    Amended from ghsa record GHSA-8r35-5x5r-hv74

  2. Revision 2 · amended ·

    Amended from osv record GHSA-8r35-5x5r-hv74

  3. Revision 1 · created ·

    Published from ghsa record GHSA-8r35-5x5r-hv74

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-87013

Advisory: Open WebUI: Any authenticated user can start a non-terminating request via a folder parent cycle
IDs: CVE-2026-87013, GHSA-8r35-5x5r-hv74
Record: https://patchnext.com/advisories/cve-2026-87013 (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 4.3)
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.10.0, <= 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-8r35-5x5r-hv74 (GitHub-reviewed advisory GHSA-8r35-5x5r-hv74 lists affected ranges: PyPI open-webui >=0.10.0 <=0.11.0)
- Verified: https://osv.dev/vulnerability/GHSA-8r35-5x5r-hv74 (OSV record GHSA-8r35-5x5r-hv74 lists affected ranges: PyPI open-webui >=0.10.0 <0.11.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…