CVE-2026-70494 open-webui CVE debrief

Who should care

Open WebUI users and administrators should be aware of this vulnerability and take steps to patch and mitigate potential risks. They should review and restrict write access to shared chat folders, monitor for suspicious deletion activities, and prioritize patching to prevent unauthorized deletion of chats and messages. Additionally, they should assess their exposure, confirm affected product deployments, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Security teams should track exceptions, retest remediated assets, and close the item only after evidence is documented. Vulnerability management and platform security teams should also review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. Operators of Open WebUI should verify their configurations and ensure that compensating controls are in place for exposed systems while remediation is scheduled and verified. Asset inventory and change management processes should be updated to reflect the necessary patches and mitigations. Monitoring and detection teams should check relevant logs for exposed assets that need extra review. Overall, a coordinated effort across IT operations, security, and compliance teams is necessary to address this vulnerability effectively. This includes confirming affected systems, applying patches, and verifying the effectiveness of compensating controls. The goal is to minimize the risk of unauthorized data deletion and ensure the integrity of chat folders and messages within the Open WebUI platform. By taking these steps, organizations can protect their data and maintain the trust and confidentiality of their communications. The vulnerability's impact on operational security and data integrity necessitates prompt attention and thorough remediation efforts. Therefore, it is crucial for all stakeholders to collaborate in the remediation process and ensure that all necessary measures are taken to prevent exploitation. This collaborative approach will help in safeguarding against potential attacks and maintaining the security posture of Open WebUI deployments. In conclusion, the affected 0

Technical summary

The DELETE /api/v1/folders/{id} handler in Open WebUI allowed users with write access to a shared chat folder to delete chats and messages belonging to the folder owner. This was due to a flawed authorization check that accepted inherited write grants for subfolders instead of requiring ownership or administrator status. The issue is fixed in version 0.11.0, which corrects the authorization logic to prevent unauthorized deletion of chats and messages.

Defensive priority

Open WebUI users should prioritize patching to prevent unauthorized deletion of chats and messages.

Recommended defensive actions

• Patch Open WebUI to version 0.11.0 or later
• Review and restrict write access to shared chat folders
• Monitor for suspicious deletion activities
• 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
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Open WebUI. The issue allows users with write access to a shared chat folder to delete chats and messages belonging to the folder owner. The fix is included in version 0.11.0. To verify, defenders should review the official advisory, assess their exposure, and confirm whether affected product deployments exist in their managed environments. They should also monitor for suspicious deletion activities and review compensating controls for exposed systems.

Official resources