NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Open WebUI

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

mediumCVSS 3.1 4.3GHSA-8r35-5x5r-hv74

Open WebUI 0.10.0 to 0.11.0 lets any logged-in user move a folder under itself, creating a loop. The next delete or read of that folder starts a request that never ends, holds a CPU core and slowly grows memory. Fixed in 0.11.1, which also repairs existing loops.

Published Sep 10, 2026 · Analysis Oct 31, 2026

What an attacker can do

Open WebUI stores folders as a parent reference per folder and assumes the tree has no cycles. The re-parent endpoint POST /api/v1/folders/{id}/update/parent did not check that the new parent differed from the folder itself or one of its subfolders. The subtree walk added in 0.10.0 did not track visited folders either. After a user sets a folder's parent_id to its own id, a DELETE /api/v1/folders/{id} or POST /api/v1/folders/{id}/read call walks the loop forever.

The attacker needs any authenticated account. Folders must be enabled (ENABLE_FOLDERS, default true), and the role needs the folders feature permission (USER_PERMISSIONS_FEATURES_FOLDERS, default true). Both are on by default.

The stuck request keeps running after the client disconnects, holds a core, and its in-memory folder list grows by about 0.6 GB per hour until restart. The loop persists in the database, so any later request on that folder restarts it. The advisory's measurements show other users stay served: each step waits on a database query, and about 900 concurrent requests were needed before anyone saw slowdown. The effect is slow resource exhaustion, not an instant outage. No data is exposed or changed.

Who is affected

The open-webui pip package from 0.10.0 up to and including 0.11.0. Earlier releases lack the subtree walk. Deployments that set ENABLE_FOLDERS to false, or remove the folders feature permission from non-admin roles, are not affected.

pip show open-webui

For Docker, check the image tag or open the About page in the admin settings.

open-webui

Ecosystem
PyPI
Affected
>= 0.10.0, <= 0.11.0
Fixed in
0.11.1
Check
pip show open-webui

How to fix it

Upgrade to open-webui 0.11.1.

pip install --upgrade open-webui==0.11.1

The fix (pull request 28748) rejects moving a folder into itself or its own subfolder with a 400, makes every folder tree walk skip ids already visited, and returns any folder whose parent chain loops to the root the next time the folder list is requested. Instances that already hold looping folders recover on upgrade with no operator action. As a workaround before upgrading, the advisory's preconditions imply you can disable folders or withhold the folders permission from non-admin roles; it names no other workaround. Restart the process to stop requests already stuck.

How to tell if you were hit

Look for requests to POST /api/v1/folders/{id}/update/parent where the body parent_id equals the id in the path, and for DELETE /api/v1/folders/{id} or POST /api/v1/folders/{id}/read calls that never log a response. On the host, watch for an Open WebUI worker pinned at one core whose memory climbs steadily, about 0.6 GB per hour per stuck request, that stays busy after clients disconnect. In the database, a folder row whose parent_id equals its own id, or whose parent chain returns to itself, confirms the loop.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

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 (ENABLE_FOLDERS, default true) and the acting user's role must hold the folders feature permission (USER_PERMISSIONS_FEATURES_FOLDERS, 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 GB per hour until the process is restarted. The folder stays in the looping state in the database, so any later request touching that folder starts the loop again.

The instance stays responsive while this happens. Each step of the walk waits on a database query, so other users continue to be served normally; measured on a default install, two concurrent instances of this request left unrelated users unaffected, and roughly 900 concurrent requests were needed before anyone else saw a slowdown. Nothing is denied to any other party at the time of the attack, and an unattended instance degrades over hours rather than immediately. No user data is exposed and no data belonging to another user is modified.

Fix

Fixed in 0.11.1 by https://github.com/open-webui/open-webui/pull/28748. Moving a folder into itself or into one of its own subfolders is now rejected with a 400, every folder tree walk skips ids it has already visited, and a folder whose parent chain loops is returned to the root the next time the folder list is requested. An instance that already holds folders in this state recovers on upgrade with no operator action.

Root cause

Affected components: the folder re-parent handler POST /api/v1/folders/{id}/update/parent, the subtree walk in the folder model that expands a folder into its descendants, and the two endpoints that call it, DELETE /api/v1/folders/{id} and POST /api/v1/folders/{id}/read. Affected setup: the subtree walk was introduced in 0.10.0, so no earlier release carries the code.

The folder hierarchy is stored as a plain parent reference per folder, with the acyclic property assumed rather than enforced. The write path never validated that assumption, and the read paths were written as if it always held, so nothing on either side would notice or stop a loop.

Proof of concept

Reproduced against a default 0.11.0 install. As an ordinary authenticated user:

  1. Create a folder and note its id.
  2. POST /api/v1/folders/{id}/update/parent with parent_id set to that same id. The request is accepted.
  3. DELETE /api/v1/folders/{id} (or POST /api/v1/folders/{id}/read). The request never returns, and the worker continues running after the client disconnects.

No data was seeded directly into the database. Every step ran through the public API.

Credits

@luida-ikura, who reported the folder parent cycle and the non-terminating subtree walk it reaches.

Credited to luida-ikura, Classic298.

Questions

Is Open WebUI 0.11.0 affected by CVE-2026-87013?

Yes. Versions 0.10.0 through 0.11.0 are affected. Version 0.11.1 fixes it.

Does the attacker need to be an admin?

No. Any authenticated account with the default folders permission is enough. No second user, shared folder or victim interaction is involved.

Will the instance go down immediately?

Not according to the advisory. Other users kept being served in the tests. The damage is a pinned core and memory growth of about 0.6 GB per hour per stuck request until a restart.

Do I need to clean up looping folders after upgrading?

No. After upgrading, folders with looping parent chains go back to the root when the folder list is next requested, so no operator action is required.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Open WebUI vulnerabilities

All Open WebUI entries