PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-59227 open-webui CVE debrief

Open WebUI, an extensible and feature-rich self-hosted AI platform, had a vulnerability in versions from 0.8.11 up to but not including 0.10.0. The issue allowed a non-admin user to invoke server-side image editing with administrator-configured provider credentials via the POST /api/v1/images/edit endpoint. This was possible because the endpoint required only a verified account and did not enforce the global image-edit switch or the per-user image-generation permission.

Vendor
open-webui
Product
Unknown
CVSS
MEDIUM 4.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-09
Original CVE updated
2026-07-14
Advisory published
2026-07-09
Advisory updated
2026-07-14

Who should care

Administrators and users of Open WebUI, especially those who have not upgraded to version 0.10.0 or later, should be aware of this vulnerability. The vulnerability could allow unauthorized server-side image editing, potentially leading to data integrity issues or other security concerns.

Technical summary

The vulnerability in Open WebUI versions 0.8.11 to 0.9.x allowed for unauthorized server-side image editing. The POST /api/v1/images/edit endpoint did not properly enforce permissions, allowing verified non-admin users to edit images using administrator-configured provider credentials. This issue was addressed in version 0.10.0. Affected deployments should be reviewed for exposure, and administrators should consider upgrading to version 0.10.0 or later to mitigate this vulnerability.

Defensive priority

Medium priority should be given to upgrading Open WebUI to version 0.10.0 or later. Additionally, administrators should review their current configurations and monitor for any suspicious image editing activities.

Recommended defensive actions

  • Upgrade Open WebUI to version 0.10.0 or later
  • Review current configurations and permissions
  • Monitor for suspicious image editing activities
  • Verify user permissions and access controls
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record was published on 2026-07-09T17:17:04.223Z and was last modified on 2026-07-14T02:16:57.267Z. The NVD entry is currently Modified. Evidence of exposure should be verified through review of system logs and configurations. Defenders should validate affected scope and vendor guidance.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-59227 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-59227

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-59227 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-59227

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.