CVE-2026-44570: open-webui · Insecure Direct Object Reference
Affects open-webuiSource GCVE Database
Not known to be exploited · CVSS 8.3 High : upgrade to 0.6.19 soon.
Data as of 12 Nov 2026, 00:17 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.3 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.19
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade open-webui to 0.6.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-webui open-webui | Affected
| Fixed in
|
AI-suggested
Upgrade open-webui to version 0.6.19 or later, where this authorization bypass vulnerability is fixed. No other mitigation is required as the fix addresses the inconsistent authorization controls.
Description
Open WebUI versions prior to 0.6.19 contain an authorization bypass vulnerability in the memories API. This flaw allows non-admin users to view, delete, and restore other users' memory data without proper authorization. The issue arises from inconsistent access controls on endpoints such as POST /api/v1/memories/query, POST /api/v1/memories/{memory_id}/update, and DELETE /api/v1/memories/{memory_id}. The vulnerability is fixed in version 0.6.19.