CVE-2026-44570
Memory API auth flaw lets non-admin view/delete others' memories.
Is CVE-2026-44570 being exploited?
Not confirmed. CVE-2026-44570 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-44570?
CVE-2026-44570 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44570?
Yes. A fix has been recorded for CVE-2026-44570. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44570 affect?
CVE-2026-44570 affects Open WebUI self-hosted AI platform, Memories API endpoints (v0.6.18 and earlier). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44570?
Upgrade to 0.6.19+, audit permissions, validate data integrity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows viewing, deleting, or restoring other users' memories via API; privacy breach.
Patch when possible
- affected< 0.6.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.