Is CVE-2026-59714 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-59714 being exploited in the wild.

How severe is CVE-2026-59714?

High severity, with a CVSS score of 7.1, published 13 August 2026.

Which products and versions are affected?

open-webui (PyPI) >= 0.9.5, < 0.10.0, ECOSYSTEM:introduced=0.9.5,fixed=0.10.0.

Is there a fix for CVE-2026-59714?

Yes. open-webui (PyPI): upgrade to 0.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-59714 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-59714?

Check whether you run open-webui (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59714: Open WebUI cross-channel message overwrite in chat completion API

Q: Is there a fix for CVE-2026-59714?

Yes. open-webui (PyPI): upgrade to 0.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-59714 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-59714?

Check whether you run open-webui (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-59714 · Severity: high · CVSS 7.1 · Published 2026-08-13

An authenticated user can overwrite messages in any chat channel, including private and direct messages they do not have permission to access. This allows an attacker to change the content of existing messages while making it appear as though the original author wrote them, potentially leading to misinformation or impersonation within the platform.

Technologies: open-webui (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-59714 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59714 being exploited in the wild.
How severe is CVE-2026-59714?: High severity, with a CVSS score of 7.1, published 13 August 2026.
Which products and versions are affected?: open-webui (PyPI) >= 0.9.5, < 0.10.0, ECOSYSTEM:introduced=0.9.5,fixed=0.10.0.
Is there a fix for CVE-2026-59714?: Yes. open-webui (PyPI): upgrade to 0.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59714 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-59714?: Check whether you run open-webui (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

open-webui (PyPI): upgrade to 0.10.0 or later
```
pip install "open-webui>=0.10.0"
```

Technical details

A missing authorization check in the chat completion API allows authenticated users to overwrite messages across different channels. When a request uses a 'channel:'-prefixed chat_id, the application skips ownership verification and passes user-supplied message IDs directly to a database update function. This function, `_make_channel_emitter`, performs updates based on the primary key without verifying if the message belongs to the specified channel or if the user has access to it. This affects both single-model requests and multimodel requests using the `message_ids` map. The vulnerability is patched in version 0.10.0 by implementing per-entry validation and a fail-closed emitter that verifies channel ownership before writing.

Affected products

Open WebUI open-webui >= 0.9.5, < 0.10.0

Identifiers

CVE-2026-59714
GHSA-x2ff-v5v8-m75m
PYSEC-2026-3605

Timeline

2026-07-02: disclosed: Initial disclosure on GitHub
2026-07-24: advisory: GitHub Advisory published
2026-07-24: patched: Fix confirmed in version 0.10.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.