open-webui Open WebUI up to 0.9.5 Prompt History resource injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 1.54 |
Summary
A vulnerability has been found in open-webui Open WebUI and classified as problematic. This issue affects some unknown processing of the component Prompt History. Performing a manipulation results in resource injection. This vulnerability is known as CVE-2026-54015. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in open-webui Open WebUI. This affects an unknown part of the component Prompt History. The manipulation with an unknown input leads to a resource injection vulnerability. CWE is classifying the issue as CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-54015. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.9.6 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 0.1.124
- 0.3.16
- 0.5.7
- 0.5.11
- 0.6.5
- 0.6.10
- 0.6.19
- 0.6.31
- 0.6.35
- 0.6.37
- 0.6.44
- 0.7.0
- 0.8.0
- 0.8.6
- 0.8.9
- 0.8.11
- 0.8.12
- 0.9.0
- 0.9.3
- 0.9.5
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource injectionCWE: CWE-99
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Open WebUI 0.9.6
Timeline
06/21/2026 Advisory disclosed06/21/2026 VulDB entry created
06/21/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-54015 (🔒)
GCVE (CVE): GCVE-0-2026-54015
GCVE (VulDB): GCVE-100-372585
Entry
Created: 06/21/2026 05:55Changes: 06/21/2026 05:55 (51)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.