Attack Chain

1. An authenticated attacker sends a POST request to the /api/chat/completions API endpoint.
2. The request body includes a chat_id parameter prefixed with channel:, for example, channel:any-channel-uuid-here, and a message_id parameter corresponding to a specific message in a target victim channel.
3. When main.py processes the request with the channel: prefix, it incorrectly bypasses the standard ownership and membership verification checks for the channel.
4. The user-supplied message_id from the request body is passed directly to the _make_channel_emitter function in socket/main.py.
5. The _make_channel_emitter function then calls Messages.update_message_by_id.
6. Messages.update_message_by_id executes a direct primary-key database update using the attacker-provided message_id without performing any additional channel ID or user authorization validation.
7. The content of the targeted message in the victim's channel is overwritten with attacker-controlled content.
8. The overwritten message retains the original author's attribution, allowing the attacker to impersonate the legitimate sender.

Impact

The successful exploitation of CVE-2026-59714 allows any authenticated user to unilaterally overwrite messages in any channel they do not belong to, including private channels and direct messages. This leads to a severe degradation of message integrity and enables sophisticated impersonation attacks, as the altered messages still appear to originate from their original authors. This could be used for spreading misinformation, issuing false instructions, or compromising the privacy and trust within an organization's communication platform. While the advisory does not specify the number of victims or sectors targeted, any organization utilizing vulnerable versions of Open WebUI is at risk of such communication integrity breaches.

Recommendation

• Patch Open WebUI instances immediately to version 0.10.0 or later to remediate CVE-2026-59714.
• Monitor application logs for POST requests to /api/chat/completions containing a chat_id parameter that starts with channel:, especially if the request is not from expected sources or user roles.
• Implement WAF or API gateway rules to inspect the JSON body of POST /api/chat/completions requests for the chat_id field containing channel: and the message_id field.
• Review access logs and internal audit trails for any POST requests to the http://target:8080/api/chat/completions endpoint that occurred on affected versions.