Quick answers
- Is CVE-2026-59224 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59224 being exploited in the wild.
- How severe is CVE-2026-59224?
- High severity, with a CVSS score of 8, published 9 July 2026.
- Which products and versions are affected?
- open-webui (PyPI) < 0.10.0, ECOSYSTEM:introduced=0,fixed=0.10.0.
- Is there a fix for CVE-2026-59224?
- Yes. open-webui (PyPI): upgrade to 0.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59224 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-59224?
- Check whether you run open-webui (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- open-webui (PyPI): upgrade to 0.10.0 or later
pip install "open-webui>=0.10.0"
Technical details
The terminal proxy in `backend/open_webui/routers/terminals.py` fails to cryptographically bind user identities to sessions when forwarding requests to upstream backends. In the HTTP path, the `X-User-Id` header is sent unsigned, allowing spoofing if the upstream is reachable via SSRF or other means. In the WebSocket path (`ws_terminal`), the `session_id` path parameter is interpolated into the upstream URL without validation or encoding. An attacker can use query injection (smuggling `?` or `&` characters) to override the `user_id` parameter. This allows a low-privileged user to attach to another user's live pseudo-terminal (PTY) if the session ID is known. The issue is fixed in version 0.10.0.
Affected products
- Open WebUI Open WebUI < 0.10.0
Identifiers
- CVE-2026-59224
- GHSA-j657-m4c4-24jq
- PYSEC-2026-3600
Timeline
- 2026-07-02: disclosed: Initial report by smoke-wolf
- 2026-07-09: advisory: NVD publication
- 2026-07-24: patched: Version 0.10.0 released