# CVE-2026-109287: Open WebUI 0.9.6 before 0.11.4 Information Disclosure via Unscoped Directory ID

> Attackers with read access to any knowledge base can expose folder names and owner IDs of other directories by supplying foreign directory IDs.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-jx3w-3pqq-7f3w, GHSA-qrjc-r6jg-4w9f

## What is CVE-2026-109287?

CVE-2026-109287 is a medium-severity missing authorization vulnerability in open-webui, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open WebUI from 0.9.6 before 0.11.4 contains an authorization flaw where the knowledge base file listing does not verify that a supplied directory_id belongs to the requested knowledge base. Users with read access to any knowledge base can supply a retained foreign directory UUID to GET /api/v1/knowledge/{id}/files. The returned breadcrumbs expose folder names, owner user ids and knowledge base ids of that directory and all its ancestors.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-109287?


## How do I fix CVE-2026-109287?

No fix has been published for CVE-2026-109287 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109287 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109287 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109287 and fix it if it is affected.

What it is: CVE-2026-109287 is a medium-severity missing authorization vulnerability in open-webui, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109287 exists.

Affected product: open-webui. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109287/ (Markdown: https://insights.sbomify.com/CVE-2026-109287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109287
- OSV: https://osv.dev/vulnerability/CVE-2026-109287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109287/
Summaries are generated and may contain mistakes; the official description above is the record.