Is this vulnerability remotely exploitable?

It can be exploited remotely if the Open WebUI instance is accessible over the network and an attacker can obtain access to an account or use any anonymous/guest capabilities. The vulnerability does not inherently require local system access.

What level of access does an attacker need to exploit it?

Typically, an attacker needs at least some level of application access (e.g., a normal user account or guest access if enabled). The broken access control then allows that user to access tool values beyond what their role or identity should normally permit.

What is the safest general fix pattern for this issue?

The safest pattern is to implement strict, server-side authorization checks for every operation involving tool values, based on resource ownership and explicit permissions. Centralize authorization logic so all tool-related endpoints pass through the same permission enforcement layer.

Severity:

HIGH RISK

(7.7)

Broken Access Control (CWE-285) in Open WebUI Tool Values

CVE-2026-34222

Published:

Apr 1, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Broken Access Control

CWE:

CWE-285

Impact:

Unauthorized Access and Manipulation of Tool Configuration or Data

Severity:

HIGH RISK

(7.7)

CVSS Version:

3.1

Vulnerability Type

Category:

Broken Access Control

CWE:

CWE-285

Impact:

Unauthorized Access and Manipulation of Tool Configuration or Data

Severity:

HIGH RISK

(7.7)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Broken Access Control (CWE-285) in Open WebUI Tool Values

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal