Skip to main content
VulnerabilityPublished Updated

CVE-2026-44570: open-webui · Insecure Direct Object Reference

Affects open-webuiSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 0.6.19 soon.

Data as of 12 Nov 2026, 00:17 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
open-webui open-webuiAffected
  • <0.6.19
Fixed in
  • 0.6.19

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.

References

Community reviews

Loading reviews…