Is CVE-2026-70490 exploited in the wild?

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

How severe is CVE-2026-70490?

Medium severity, with a CVSS score of 6.3, published 4 August 2026.

Which products and versions are affected?

open-webui (PyPI) >= 0.8.8, < 0.11.0, ECOSYSTEM:introduced=0.8.8,fixed=0.11.0.

Is there a fix for CVE-2026-70490?

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

How is CVE-2026-70490 attacked?

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

Am I affected by CVE-2026-70490?

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-70490: Open WebUI authorization bypass in terminal WebSocket route

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

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

Q: How is CVE-2026-70490 attacked?

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

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

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-70490 · Severity: medium · CVSS 6.3 · Published 2026-08-04

Open WebUI, a user interface for interacting with large language models, contains a flaw where unapproved or deactivated user accounts can still access interactive terminal sessions. This allows users who should be restricted to execute commands, browse files, and use terminal-based tools. The issue occurs because the terminal's communication channel does not properly verify the user's approval status, potentially leading to unauthorized access to the underlying server environment.

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

Quick answers

Is CVE-2026-70490 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70490 being exploited in the wild.
How severe is CVE-2026-70490?: Medium severity, with a CVSS score of 6.3, published 4 August 2026.
Which products and versions are affected?: open-webui (PyPI) >= 0.8.8, < 0.11.0, ECOSYSTEM:introduced=0.8.8,fixed=0.11.0.
Is there a fix for CVE-2026-70490?: Yes. open-webui (PyPI): upgrade to 0.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-70490 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-70490?: 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.11.0 or later
```
pip install "open-webui>=0.11.0"
```

Technical details

An authorization bypass exists in the terminal WebSocket route of Open WebUI. While standard HTTP terminal routes use a dependency chain that enforces a 'verified_user' role check, the WebSocket route (/{server_id}/api/terminals/{session_id}) reimplements authentication inline and fails to verify the user's role status from the database. Consequently, accounts with a 'pending' status—either newly registered or recently deactivated—can establish interactive sessions if they possess a valid JWT and the terminal server is configured with broad access grants. This vulnerability stems from inconsistent authorization logic between HTTP and WebSocket code paths. The issue is resolved in version 0.11.0 by consolidating authentication into a shared helper.

Affected products

Open WebUI open-webui >= 0.8.8, < 0.11.0

Identifiers

CVE-2026-70490
GHSA-5gpj-vj23-vhhv
PYSEC-2026-3642

Timeline

2026-08-02: disclosed: Initial report/publication date
2026-08-04: advisory: GitHub Advisory published
2026-08-04: patched: Fix confirmed in version 0.11.0

References

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