GHSA-3WGJ-C2HG-VM6Q

GHSA-3WGJ-C2HG-VM6Q is a high-severity improper input validation vulnerability in open-webui (pip), affecting versions <= 0.9.4. It is fixed in 0.9.5.

Summary

Open WebUI vulnerable to stored XSS via OAuth picture claim stored as SVG data URI in profileimageurl

Impact

  • Account takeover of any authenticated user who opens the crafted URL.
  • Post-takeover: access to the victim's chats, API keys stored in their settings, and, if the victim has workspace.tools permission, RCE via installed tools (per CVE-2025-64496 analysis).
  • The same _process_picture_url function has no SSRF allowlist; a secondary primitive is to point the picture claim at an internal URL (metadata service, internal admin panel) and read the response bytes via the profile image endpoint.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

GHSA-3WGJ-C2HG-VM6Q has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.9.5); upgrading removes the vulnerable code path.

Affected versions

open-webui (<= 0.9.4)

Security releases

open-webui → 0.9.5 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

  1. In _process_picture_url (utils/oauth.py:1336-1345): reject any MIME outside {image/png, image/jpeg, image/gif, image/webp}. Use the upstream Content-Type response header, not the URL extension. Also add an SSRF allowlist or at minimum block RFC1918 / link-local / loopback targets.

  2. In get_user_profile_image_by_id (routers/users.py:504-528): enforce a MIME whitelist before building StreamingResponse. This is the defense-in-depth layer that should have caught the bypass.

  3. Apply validate_profile_image_url at the model/storage layer (Users.update_user_profile_image_url_by_id), not only at the Pydantic form layer. All write paths to the profile image column should go through the same validator.

  4. Set X-Content-Type-Options: nosniff and a default CSP unless the operator explicitly disables them.

Frequently Asked Questions

  1. What is GHSA-3WGJ-C2HG-VM6Q? GHSA-3WGJ-C2HG-VM6Q is a high-severity improper input validation vulnerability in open-webui (pip), affecting versions <= 0.9.4. It is fixed in 0.9.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
  2. How severe is GHSA-3WGJ-C2HG-VM6Q? GHSA-3WGJ-C2HG-VM6Q has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of open-webui are affected by GHSA-3WGJ-C2HG-VM6Q? open-webui (pip) versions <= 0.9.4 is affected.
  4. Is there a fix for GHSA-3WGJ-C2HG-VM6Q? Yes. GHSA-3WGJ-C2HG-VM6Q is fixed in 0.9.5. Upgrade to this version or later.
  5. Is GHSA-3WGJ-C2HG-VM6Q exploitable, and should I be worried? Whether GHSA-3WGJ-C2HG-VM6Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-3WGJ-C2HG-VM6Q is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-3WGJ-C2HG-VM6Q? Upgrade open-webui to 0.9.5 or later.

Other vulnerabilities in open-webui

CVE-2026-54022CVE-2026-54021CVE-2026-54019CVE-2026-54018CVE-2026-54017

Stop the waste.
Protect your environment with Kodem.