Open WebUI's Insecure Direct Object Reference (IDOR) allows access to other users' memories
CVE-2026-29071GHSA-w9f8-gxf9-rhvw
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.8.6), 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.8.5
- Fixed in
- 0.8.6
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-w9f8-gxf9-rhvw lists affected ranges: PyPI open-webui >=0 <0.8.6 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w9f8-gxf9-rhvw lists affected ranges: PyPI open-webui >=0 <=0.8.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-29071: 0.26% estimated exploitation activity in the next 30 days; percentile 18.17 (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 read other users' private memories via /api/v1/retrieval/query/collection Details Vulnerability 1: Missing authorization in collection querying In backend/openwebui/routers/retrieval.py, the querycollectionhandler function accepts a list of collectionnames but performs no ownership validation: Collection names follow predictable patterns: - User files: file-{FILEUUID} - User memories: user-memory-{USERUUID} (requires Memory experimental feature) PoC Environment: Open WebUI v0.8.3, default configuration. Setup: 1. Register two users: admin (first user) and attacker (second user). 2. As admin, upload a PDF document through chat. 3. As admin, enable Memory (Settings → Personalization → Memory) and add some memories. Exploitation — Step 1: Enumerate all users Response reveals all users including admin's UUID, email, and role: <img width="1340" height="731" alt="1poc - users"…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-w9f8-gxf9-rhvw
- Revision 1 · created ·
Published from osv record GHSA-w9f8-gxf9-rhvw
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-29071 Advisory: Open WebUI's Insecure Direct Object Reference (IDOR) allows access to other users' memories IDs: CVE-2026-29071, GHSA-w9f8-gxf9-rhvw Record: https://patchnext.com/advisories/cve-2026-29071 (revision 2, source checked 26 Oct 2026, 13:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.1) 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.8.6. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected <= 0.8.5; fixed in 0.8.6 ## 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://osv.dev/vulnerability/GHSA-w9f8-gxf9-rhvw (OSV record GHSA-w9f8-gxf9-rhvw lists affected ranges: PyPI open-webui >=0 <0.8.6 (fixed)) - Verified: https://github.com/advisories/GHSA-w9f8-gxf9-rhvw (GitHub-reviewed advisory GHSA-w9f8-gxf9-rhvw lists affected ranges: PyPI open-webui >=0 <=0.8.5) Commands are suggestions: review each one before running it.
Loading voting…