Open WebUI: Unauthenticated endpoint can trigger embedding generation (cost/DoS)
CVE-2026-45667GHSA-m69w-p7m4-585j
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.8.0), 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.7.2
- Fixed in
- 0.8.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-m69w-p7m4-585j lists affected ranges: PyPI open-webui >=0 <0.8.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-m69w-p7m4-585j lists affected ranges: PyPI open-webui >=0 <=0.7.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
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- EPSS
- CVE-2026-45667: 0.34% estimated exploitation activity in the next 30 days; percentile 27.71 (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 GET /api/v1/memories/ef is accessible without authentication and executes request.app.state.EMBEDDINGFUNCTION(...). This allows any unauthenticated caller to trigger embedding generation which can lead to direct cost exposure if a paid provider is used. Code reference: backend/openwebui/routers/memories.py (@router.get("/ef") - calls request.app.state.EMBEDDINGFUNCTION("hello world")). Details GET /api/v1/memories/ef is reachable without authentication and triggers request.app.state.EMBEDDINGFUNCTION("hello world"). This crosses an intended security boundary by allowing unauthenticated users to invoke potentially expensive embedding computation and/or paid upstream embedding APIs. PoC 1. Start Open WebUI in default configuration (no special env hardening; default ENABLEMEMORIES is true). 2. From an unauthenticated client (no cookies/Authorization header), call: curl -i http://\<host\:\<port\/api/v1/memories/ef 3. Observe the server performs embedding generation and returns a…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-m69w-p7m4-585j
- Revision 1 · created ·
Published from osv record GHSA-m69w-p7m4-585j
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-45667 Advisory: Open WebUI: Unauthenticated endpoint can trigger embedding generation (cost/DoS) IDs: CVE-2026-45667, GHSA-m69w-p7m4-585j Record: https://patchnext.com/advisories/cve-2026-45667 (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.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected <= 0.7.2; fixed in 0.8.0 ## 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-m69w-p7m4-585j (OSV record GHSA-m69w-p7m4-585j lists affected ranges: PyPI open-webui >=0 <0.8.0 (fixed)) - Verified: https://github.com/advisories/GHSA-m69w-p7m4-585j (GitHub-reviewed advisory GHSA-m69w-p7m4-585j lists affected ranges: PyPI open-webui >=0 <=0.7.2) Commands are suggestions: review each one before running it.
Loading voting…