Live › vulnerability › CVE-2024-7041
Go to dashboardOpen WebUI's memory update endpoint does not check that the caller owns the memory, so a logged-in user can change memories belonging to other users. An attacker gets write access to other users' stored memory content.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 15:12 UTC, 1h before NVD. All times on this page are UTC.
Teams that run Open WebUI with multiple user accounts and the memories feature in use are exposed, since any authenticated user can reach the memory update endpoint. Single-user deployments where only one person has an account are much less exposed, and teams on or later are not affected.
0.6.3| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| open-webui | pypi | < 0.6.3 | 0.6.3 |
| openwebui open webui | vendor | = 0.3.8 | – |
pip show open-webui and compare it to 0.6.3./api/v1/memories/{id}/update to see whether it verifies the memory belongs to the requesting user.open-webui to 0.6.3 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
An Insecure Direct Object Reference (IDOR) vulnerability exists in open-webui/open-webui version v0.3.8. The vulnerability occurs in the API endpoint http://0.0.0.0:3000/api/v1/memories/{id}/update, where the decentralization design is flawed, allowing attackers to edit other users' memories without proper authorization.
This page as .md · .json · in your agent: get_signal("CVE-2024-7041")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.