# CVE-2026-34225: Open WebUI has Blind Server Side Request Forgery in its Image Edit Functionality > Attackers can perform blind SSRF to scan local network ports and potentially interact with internal services via the image editing feature. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 14 Apr 2026 - **Updated:** 14 Apr 2026 - **Also known as:** GHSA-jgx9-jr5x-mvpv, PYSEC-2026-2740 ## What is CVE-2026-34225? CVE-2026-34225 is a medium-severity server-side request forgery vulnerability in Openwebui Open Webui, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Versions 0.7.2 and below contain a Blind Server Side Request Forgery in the functionality that allows editing an image via a prompt. The affected function performs a GET request to a user-provided URL with no restriction on the domain, allowing the local address space to be accessed. Since the SSRF is blind (the response cannot be read), the primary impact is port scanning of the local network, as whether a port is open can be determined based on whether the GET request succeeds or fails. These response differentials can be automated to iterate through the entire port range and identify open ports. If the service running on an open port can be inferred, an attacker may be able to interact with it in a meaningful way, provided the service offers state-changing GET request endpoints. This issue was unresolved at the time of publication. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-34225? 3 open source packages ship an affected version, including open-webui. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `open-webui` | PyPI | All versions to 0.7.2 | None | | `open-webui` | PyPI | All versions to 0.7.2 | None | | `open-webui` | PyPI | All versions to 0.7.2 | None | Products: Openwebui Open Webui. ## How do I fix CVE-2026-34225? No fix has been published for CVE-2026-34225 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-34225 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34225 exists. ## Other vulnerabilities in Openwebui Open Webui - [CVE-2026-44551](https://insights.sbomify.com/CVE-2026-44551/): Open WebUI: LDAP Empty Password Authentication Bypass (critical 9.1) - [CVE-2026-56400](https://insights.sbomify.com/CVE-2026-56400/): open-webui - Remote Code Execution via CORS Misconfiguration and Session Validation (critical 9.0) - [CVE-2024-8017](https://insights.sbomify.com/CVE-2024-8017/): Cross-site Scripting (XSS) in open-webui/open-webui (critical 9.0) - [CVE-2026-45672](https://insights.sbomify.com/CVE-2026-45672/): Open WebUI: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed (high 8.8) - [CVE-2026-87995](https://insights.sbomify.com/CVE-2026-87995/): Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-34225 and fix it if it is affected. What it is: CVE-2026-34225 is a medium-severity server-side request forgery vulnerability in Openwebui Open Webui, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34225 exists. Affected packages and fixed versions: - open-webui (PyPI): affected all versions up to 0.7.2; no fix listed - open-webui (PyPI): affected all versions up to 0.7.2; no fix listed - open-webui (PyPI): affected all versions up to 0.7.2; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-34225/ (Markdown: https://insights.sbomify.com/CVE-2026-34225/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34225 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34225 - OSV: https://osv.dev/vulnerability/CVE-2026-34225 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-34225/ Summaries are generated and may contain mistakes; the official description above is the record.