Open WebUI: Read-Only Users Can Toggle Note Pin Status via Incorrect Permission Check (Write via Read-Only Access)
CVE-2026-45316GHSA-jx2x-j75f-xq3j
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.9.3), 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.9.2
- Fixed in
- 0.9.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jx2x-j75f-xq3j lists affected ranges: PyPI open-webui >=0 <0.9.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jx2x-j75f-xq3j lists affected ranges: PyPI open-webui >=0 <=0.9.2
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.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
- EPSS
- CVE-2026-45316: 0.24% estimated exploitation activity in the next 30 days; percentile 14.59 (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 POST /api/v1/notes/{id}/pin endpoint performs a write operation (toggling the ispinned field) but only checks for read permission. Users with read-only access to a shared note can pin/unpin it, which is a state-modifying action that should require write permission. All other write endpoints (update, delete, access/update) correctly check for write permission. Details Affected code: backend/openwebui/routers/notes.py lines 412-444 Compare with update endpoint (correct, line 318-327): PoC Environment: Open WebUI v0.9.2, default configuration with notes sharing enabled. Setup: 1. UserA creates a note 2. UserA shares note with UserB with read permission via POST /api/v1/notes/{id}/access/update with {"accessgrants":[{"principaltype":"user","principalid":"USERBID","permission":"read"}]} Test: E2E Verified Result: - Step 1: UserB reads note (READ) - 200 OK ✓ - Step 2: UserB updates note (WRITE) - 403 Forbidden ✓ (correctly blocked) - Step 3: UserB pins note (WRITE via READ) -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-jx2x-j75f-xq3j
- Revision 1 · created ·
Published from osv record GHSA-jx2x-j75f-xq3j
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-45316 Advisory: Open WebUI: Read-Only Users Can Toggle Note Pin Status via Incorrect Permission Check (Write via Read-Only Access) IDs: CVE-2026-45316, GHSA-jx2x-j75f-xq3j Record: https://patchnext.com/advisories/cve-2026-45316 (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: Low (CVSS 3.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.9.3. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected <= 0.9.2; fixed in 0.9.3 ## 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-jx2x-j75f-xq3j (OSV record GHSA-jx2x-j75f-xq3j lists affected ranges: PyPI open-webui >=0 <0.9.3 (fixed)) - Verified: https://github.com/advisories/GHSA-jx2x-j75f-xq3j (GitHub-reviewed advisory GHSA-jx2x-j75f-xq3j lists affected ranges: PyPI open-webui >=0 <=0.9.2) Commands are suggestions: review each one before running it.
Loading voting…