Open WebUI · weakness class
Server-Side Request Forgery
16 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 16 is a mark on the map. Named now: 1 to 16, most at risk first.
- Open WebUI vulnerable to Server-Side Request Forgery (SSRF) via Arbitrary URL Processing in /api/v1/retrieval/process/web
- Open WebUI: SSRF into internal services via unvalidated sub-resource requests in the Playwright web loader
- Open WebUI - Server-Side Request Forgery via Location Redirect in /api/v1/retrieval/process/web
- Open WebUI vulnerable to server-side request forgery in utils.py
- Open WebUI: SSRF via OAuth Profile Picture URL in _process_picture_url (oauth.py)
- Open WebUI: SSRF Protection Bypass in Playwright Web Loader via HTTP Redirects
- Open WebUI: Server-side fetches reach blocked and internal hosts via unvalidated HTTP redirect targets
- Open WebUI: Any authenticated user can reach the Azure platform channel via server-side web fetch
- Open WebUI: Any authenticated user can reach internal services and cloud metadata via NAT64-encoded URLs
- Open WebUI: Client-side SSRF via unrestricted external resource loading in Vega/Vega-Lite chart rendering
- Open WebUI: Redirect-Bypass SSRF in OAuth `_process_picture_url`
- Open WebUI: SSRF Bypass via HTTP Redirect Following in Web-Fetch and Image-Load Endpoints
- Open WebUI has Blind Server Side Request Forgery in its Image Edit Functionality
- Open WebUI: Server-Side Request Forgery (SSRF) bypass in `validate_url`
- Open WebUI: Full SSRF Vulnerability in the RAG Web Search Feature
- Open WebUI: Blind server side request forgery (SSRF) via the PDF generate function
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.