What is the CVSS score of EUVD-2026-42630?

EUVD-2026-42630 has a CVSS 3.1 base score of 3.1 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.3%.

Is there a public PoC exploit available for EUVD-2026-42630?

Yes, a public proof-of-concept exploit is available for EUVD-2026-42630. Prioritise patching immediately. EPSS: 0.3%.

Is there a patch available for EUVD-2026-42630?

Yes, a patch is available for EUVD-2026-42630. Update the affected software to the latest version immediately.

Open WebUI EUVD-2026-42630

| CVE-2026-59215 LOW

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-07-09 security-advisories@github.com

GHSA-73x5-h92w-xc2j

Authentication Bypass Open Webui Openwebui

3.1

CVSS 3.1 · Vendor: github

Severity by source

Vendor (github) PRIMARY

3.1 LOW

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

vuln.today AI

3.1 LOW

Network-accessible IDOR requiring an authenticated low-privilege account (PR:L) and knowledge of cross-channel message IDs (AC:H); impact is read-only thread context disclosure with no integrity or availability effect.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Jul 09, 2026 - 18:01 EUVD

Analysis Generated

Jul 09, 2026 - 17:42 vuln.today

DescriptionCVE.org

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.10.0, channel thread parent and reply handling did not bind parent_id to the channel in the URL, allowing an authenticated user to reference a message from another private or DM channel and disclose thread context across channels. This issue is fixed in version 0.10.0.

AnalysisAI

Cross-channel thread context disclosure in Open WebUI prior to 0.10.0 allows authenticated low-privilege users to reference messages from private or DM channels they do not have access to, leaking thread content across channel boundaries. The root cause is a missing channel-binding validation on the parent_id parameter in thread reply handling - the server does not verify that the referenced parent message belongs to the channel specified in the URL. No public exploit or active exploitation has been identified; this is a low-severity, high-complexity authorization bypass with confirmed vendor fix in v0.10.0.

Technical ContextAI

The vulnerability is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), an IDOR-class flaw where a user-controlled identifier - here, the parent_id referencing a thread's parent message - is processed by the server without verifying the caller's authorization to the object in its proper channel context. Open WebUI is a self-hosted AI platform built around extensible chat interfaces with support for channels, threads, and direct messaging. The threading subsystem accepts a parent_id in requests to create or retrieve thread replies, but fails to bind that identifier to the channel specified in the URL path. This allows an authenticated user to supply a parent_id sourced from a private or DM channel they are not a member of, and the server will process and return that channel's thread context without an authorization check. No CPE strings were provided in the input data.

RemediationAI

Upgrade Open WebUI to version 0.10.0 or later, which resolves the issue per the vendor security advisory GHSA-73x5-h92w-xc2j. The underlying fix is implemented in commit a66477b7104c5d141ce7bffaea424b43e7666ef1 via pull request #25766. For deployments unable to upgrade immediately, the most effective compensating control is restricting the Open WebUI instance to a fully trusted user population - eliminating the low-privilege account vector (PR:L) removes the attack surface entirely, though this may impact normal operations. Additionally, reviewing and minimizing user account provisioning reduces the number of principals capable of exploiting cross-channel ID references. There is no known workaround that preserves full functionality while blocking this specific flaw at the application layer without patching.