CVE-2026-59227

Open WebUI: POST /api/v1/images/edit bypasses the global image-edit switch and the per-user image-generation permission

POST /api/v1/images/edit
Authorization: Bearer <non_admin_user_token>
Content-Type: application/json

{"image":"data:image/png;base64,<png>","prompt":"edit","model":"gpt-image-1"}

An authenticated, non-admin user can:

• bypass the global ENABLE_IMAGE_EDIT=False administrator control;
• bypass a denied per-user/group features.image_generation permission;
• cause the server to send billable image-edit requests to the configured provider (OpenAI-compatible, Gemini, or ComfyUI) using administrator-configured credentials (IMAGES_EDIT_OPENAI_API_KEY for the OpenAI engine).

No cross-user data is exposed and the provider credentials are never returned to the caller; the impact is the control/permission bypass and the associated billable resource consumption.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-59227 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. 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.10.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The direct route is split from its shared implementation (mirroring generate_images/image_generations): a thin /edit route now enforces ENABLE_IMAGE_EDIT and the per-user features.image_generation permission before delegating to the shared image_edits() implementation. The internal callers (the edit_image tool and the chat middleware) call the implementation directly and already gate themselves, so they are unaffected.

1. What is CVE-2026-59227? CVE-2026-59227 is a medium-severity missing authorization vulnerability in open-webui (pip), affecting versions >= 0.8.11, < 0.10.0. It is fixed in 0.10.0. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-59227? CVE-2026-59227 has a CVSS score of 4.3 (Medium). 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 CVE-2026-59227? open-webui (pip) versions >= 0.8.11, < 0.10.0 is affected.
4. Is there a fix for CVE-2026-59227? Yes. CVE-2026-59227 is fixed in 0.10.0. Upgrade to this version or later.
5. Is CVE-2026-59227 exploitable, and should I be worried? Whether CVE-2026-59227 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 CVE-2026-59227 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 CVE-2026-59227? Upgrade open-webui to 0.10.0 or later.

Other vulnerabilities in open-webui