Open WebUI has an Indirect Object Reference (IDOR) in user notes
CVE-2026-45666GHSA-x3qm-p8hr-3c3h
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.8.11), 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.10
- Fixed in
- 0.8.11
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-x3qm-p8hr-3c3h lists affected ranges: PyPI open-webui >=0 <0.8.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-x3qm-p8hr-3c3h lists affected ranges: PyPI open-webui >=0 <=0.8.10
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
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-45666: 0.28% estimated exploitation activity in the next 30 days; percentile 20.24 (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 The API /api/v1/notes/{noteid} endpoint lacks proper authorization checks, allowing authenticated users to retrieve notes belonging to other users by guessing or enumerating UUIDs. This results in unauthorized disclosure of potentially sensitive or private user data. Details - if notes is enabled from UI (Settings General Features Notes (Beta)) - From API, attacker can access other user notes - if notes is disabled from UI (Settings General Features Notes (Beta)) - Then attacker can enable the notes from /api/config and access other user notes PoC - Step 1: Log in to the application as a valid user (User A). - Step 2: Intercept or inspect the response from the endpoint GET /api/config. - Step 3: Observe the field "enablenotes": false in the JSON response. - Step 4: Manually change "enablenotes" to true using browser DevTools or by intercepting and modifying the response via a proxy like Burp Suite. (Please note, the occurrence of this API comes twice, hence modification needs…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-x3qm-p8hr-3c3h
- Revision 1 · created ·
Published from osv record GHSA-x3qm-p8hr-3c3h
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-45666 Advisory: Open WebUI has an Indirect Object Reference (IDOR) in user notes IDs: CVE-2026-45666, GHSA-x3qm-p8hr-3c3h Record: https://patchnext.com/advisories/cve-2026-45666 (revision 2, source checked 26 Oct 2026, 13:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) 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.11. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected <= 0.8.10; fixed in 0.8.11 ## 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-x3qm-p8hr-3c3h (OSV record GHSA-x3qm-p8hr-3c3h lists affected ranges: PyPI open-webui >=0 <0.8.11 (fixed)) - Verified: https://github.com/advisories/GHSA-x3qm-p8hr-3c3h (GitHub-reviewed advisory GHSA-x3qm-p8hr-3c3h lists affected ranges: PyPI open-webui >=0 <=0.8.10) Commands are suggestions: review each one before running it.
Loading voting…