Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-109287 Overview
CVE-2026-109287 is an authorization flaw in Open WebUI versions 0.9.6 through 0.11.3. The knowledge base file listing endpoint fails to verify that a supplied directory_id belongs to the requested knowledge base. Users with read access to any knowledge base can pass a retained foreign directory UUID to GET /api/v1/knowledge/{id}/files and retrieve breadcrumb metadata from unrelated directories. The returned data exposes folder names, owner user IDs, and knowledge base IDs for the target directory and all ancestors. The weakness maps to CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Authenticated users can enumerate folder names, owner identifiers, and knowledge base IDs across tenants or workspaces they do not own.
Affected Products
- Open WebUI 0.9.6 through 0.11.3
- Deployments exposing /api/v1/knowledge/{id}/files to multi-tenant users
- Self-hosted Open WebUI instances with shared knowledge bases
Discovery Timeline
- 2026-10-12 - CVE-2026-109287 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-109287
Vulnerability Analysis
Open WebUI exposes a knowledge base file listing endpoint at GET /api/v1/knowledge/{id}/files. The handler accepts a directory_id query parameter used to build breadcrumb navigation. The server verifies that the caller can read the knowledge base identified by {id} in the path. It does not verify that the supplied directory_id is a child of that knowledge base.
An authenticated user with read access to any one knowledge base can therefore submit a directory_id that belongs to a different knowledge base. The breadcrumb builder walks the directory ancestry and returns folder names, owner user IDs, and parent knowledge base identifiers in the response. This disclosure crosses tenant and ownership boundaries defined inside the application.
The flaw affects confidentiality only. Attackers cannot modify data or escalate privileges through this endpoint. However, the leaked metadata can support reconnaissance against other users and workspaces hosted on the same instance.
Root Cause
The root cause is a missing scope check between the path parameter {id} and the query parameter directory_id. The authorization model trusts the caller-supplied directory UUID as a navigation hint rather than as a security-sensitive object reference. This matches the [CWE-639] pattern of authorization bypass through a user-controlled key.
Attack Vector
Exploitation requires network access to the Open WebUI API and valid credentials with read access to at least one knowledge base. The attacker needs a previously observed or guessed directory_id UUID from another knowledge base. The attacker then calls GET /api/v1/knowledge/{id}/files?directory_id={foreign_uuid} and parses the returned breadcrumbs for folder names, owner IDs, and ancestor knowledge base IDs.
No exploitation code is published for CVE-2026-109287. Technical detail is available in the GitHub Security Advisory GHSA-jx3w-3pqq-7f3w and the Vulncheck Advisory.
Detection Methods for CVE-2026-109287
Indicators of Compromise
- Requests to GET /api/v1/knowledge/{id}/files where the directory_id query parameter resolves to a knowledge base other than {id}.
- Repeated requests from a single authenticated session enumerating different directory_id UUIDs against the same knowledge base path.
- Response payloads containing breadcrumb entries whose parent knowledge base IDs do not match the request path.
Detection Strategies
- Instrument the Open WebUI API layer to log knowledge_id from the path and directory_id from the query string, then flag mismatches.
- Correlate authenticated user IDs against the owner IDs returned in breadcrumbs and alert when a user reads directories owned by another account.
- Baseline normal breadcrumb traffic per user and alert on sudden spikes in file-listing calls with varying directory_id values.
Monitoring Recommendations
- Forward Open WebUI reverse proxy logs to a central SIEM and retain full URL query strings for the knowledge API routes.
- Review access logs for unauthenticated or low-privilege accounts hitting /api/v1/knowledge/ endpoints at elevated rates.
- Track Open WebUI version strings reported by deployments and alert on any instance still running 0.9.6 through 0.11.3.
How to Mitigate CVE-2026-109287
Immediate Actions Required
- Upgrade all Open WebUI deployments to version 0.11.4 or later, which enforces scope validation on directory_id.
- Audit knowledge base membership and remove read access for accounts that do not require it.
- Rotate or invalidate shared knowledge base links that may have exposed directory UUIDs to untrusted users.
Patch Information
The fix is included in Open WebUI 0.11.4. Patched builds validate that the supplied directory_id belongs to the knowledge base identified in the request path before returning breadcrumb data. Refer to GitHub Security Advisory GHSA-jx3w-3pqq-7f3w for the official advisory.
Workarounds
- Restrict network access to the Open WebUI API to trusted users while the upgrade is scheduled.
- Place a reverse proxy rule that rejects GET /api/v1/knowledge/{id}/files requests containing a directory_id parameter until the patch is applied.
- Limit knowledge base sharing so that only trusted collaborators hold any read access, reducing the pool of users who can abuse the endpoint.
# Example reverse proxy rule (nginx) to block the vulnerable parameter
location ~ ^/api/v1/knowledge/[^/]+/files$ {
if ($arg_directory_id) { return 403; }
proxy_pass http://open_webui_upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

