Open WebUI vulnerable to blind server side request forgery (SSRF) via the PDF generate function
CVE-2026-45347GHSA-f776-fp4w-266c
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (open-webui 0.5.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.5.11
- Fixed in
- 0.5.11
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-f776-fp4w-266c lists affected ranges: PyPI open-webui >=0 <0.5.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f776-fp4w-266c lists affected ranges: PyPI open-webui >=0 <0.5.11
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
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- EPSS
- CVE-2026-45347: 0.19% estimated exploitation activity in the next 30 days; percentile 8.23 (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 Blind server side request forgery (SSRF) via the PDF generate function. The finding resulted from a penetration test for a customer. It is suspected that the root cause of the issue lies within the core of Open WebUI, which is why it is being reported as a security issue here. Tested on Open WebUI 0.5.4. Details In the PDF export, user inputs are interpreted as HTML and embedded into the PDF. According to tests, scripts and some potentially dangerous tags (iFrame, Object, etc.) are blocked, preventing server-side content from being read through this vulnerability. However, an image tag can be used to force a server-side request (SSRF), as shown in the following below. PoC Start a chat and export the PDF: Intercept the request and insert an <img tag into the title: A HTTPS callback was received at https://d5jok0s7ghl1p77v5brlqlxwmnsega4z.oastify.com. Impact A user can force server-side GET requests. During the available testing time, no method was found to read the responses…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-f776-fp4w-266c
- Revision 1 · created ·
Published from osv record GHSA-f776-fp4w-266c
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-45347 Advisory: Open WebUI vulnerable to blind server side request forgery (SSRF) via the PDF generate function IDs: CVE-2026-45347, GHSA-f776-fp4w-266c Record: https://patchnext.com/advisories/cve-2026-45347 (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 4.3) 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.5.11. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI open-webui: affected < 0.5.11; fixed in 0.5.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-f776-fp4w-266c (OSV record GHSA-f776-fp4w-266c lists affected ranges: PyPI open-webui >=0 <0.5.11 (fixed)) - Verified: https://github.com/advisories/GHSA-f776-fp4w-266c (GitHub-reviewed advisory GHSA-f776-fp4w-266c lists affected ranges: PyPI open-webui >=0 <0.5.11) Commands are suggestions: review each one before running it.
Loading voting…