Quick answers
- Is CVE-2026-109294 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109294 being exploited in the wild.
- How severe is CVE-2026-109294?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- Open WebUI 0.6.42 before 0.11.4.
- Is there a fix for CVE-2026-109294?
- Yes: fixed in 0.11.4. Until then: Restrict network access to Open WebUI or limit which users can send chat messages until an upgrade to 0.11.4 is deployed. The fix reads responses incrementally, disables automatic decompression, and rejects any compressed response before inlining. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109294 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109294?
- Check whether you run Open WebUI 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
- Fixed in: 0.11.4
Restrict network access to Open WebUI or limit which users can send chat messages until an upgrade to 0.11.4 is deployed. The fix reads responses incrementally, disables automatic decompression, and rejects any compressed response before inlining.
Technical details
The get_image_base64_from_url function in Open WebUI reads HTTP response bodies entirely into memory before encoding them, with no size limits. An attacker-controlled server can send gzip-encoded content that decompresses to gigabytes in the server process; HTTP transparent decompression applies before any checks. The vulnerability exists in both synchronous (pre-0.9.0) and asynchronous implementations, and requests can be repeated unbounded.
Affected products
- Open WebUI Open WebUI 0.6.42 before 0.11.4
Timeline
- 2026-09-27: disclosed
- 2026-10-12: patched