CVE-2026-70483 open-webui CVE debrief

Who should care

Administrators and users of Open WebUI, especially those with multi-user environments, should be aware of this vulnerability and take necessary actions to protect their systems. They should verify and limit chat IDs accessible to authenticated users, implement checks to prevent unauthorized task abortion, and monitor for suspicious activity. Additionally, they should review compensating controls for exposed systems while remediation is scheduled and verified, and track exceptions, retest remediated assets, and close the item only after evidence is documented. Security teams should also review the vulnerability and assess their organization's exposure, and consider implementing additional security measures such as asset inventory and source tracking to mitigate potential risks associated with this vulnerability. Security teams should also consider reviewing relevant monitoring, detection, and logs for exposed assets that need extra review. Finally, security teams should also consider confirming whether affected product deployments exist in managed environments and assign an owner for follow-up. Security teams should also review vendor-supported updates or mitigations through normal change control where exposure is confirmed. Security teams should also consider planning compensating controls for exposed systems while remediation is scheduled and verified. Security teams should also consider checking relevant monitoring, detection, and logs for exposed assets that need extra review. Security teams should also consider tracking exceptions, retest remediated assets, and close the item only after evidence is documented. Security teams should also consider confirming whether affected product deployments exist in managed environments and assign an owner for follow-up. Security teams should also consider reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Security teams should also consider planning vendor-supported updates or mitigations through normal change control where exposure is confirmed. Security teams should also consider reviewing compensating controls for exposed systems while remediation is schedu

Technical summary

Open WebUI versions from 0.9.6 to 0.11.0 contain a vulnerability allowing authenticated users to abort other users' running model responses, title generation, or tag generation tasks using DELETE /api/v1/chats/{id}. The issue is fixed in version 0.11.0, and administrators should update to this version or later. In the meantime, implement checks to prevent unauthorized task abortion and monitor for suspicious DELETE /api/v1/chats/{id} requests.

Defensive priority

Authenticated users with chat IDs should verify model response, title generation, and tag generation tasks.

Recommended defensive actions

• Verify and limit chat IDs accessible to authenticated users.
• Implement checks to prevent unauthorized task abortion.
• Monitor for suspicious DELETE /api/v1/chats/{id} requests.
• Update to Open WebUI version 0.11.0 or later.
• Restrict access to sensitive chat data and tasks.

Evidence notes

Evidence from official CVE and NVD records indicate an issue in Open WebUI versions from 0.9.6 to 0.11.0, allowing authenticated users to abort other users' running model responses, title generation, or tag generation tasks using DELETE /api/v1/chats/{id}. The issue was publicly disclosed and fixed in version 0.11.0. Users should verify model response, title generation, and tag generation tasks and limit chat IDs accessible to authenticated users.

Official resources