The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service.
Metrics
Affected Vendors & Products
References
History
Tue, 12 May 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unauthenticated Deletion of Memory Records in mem0 Server | |
| Weaknesses | CWE-284 |
Tue, 12 May 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mem0ai
Mem0ai mem0 |
|
| Vendors & Products |
Mem0ai
Mem0ai mem0 |
Tue, 12 May 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-05-12T17:20:55.541Z
Reserved: 2026-03-09T00:00:00.000Z
Link: CVE-2026-31241
No data.
Status : Received
Published: 2026-05-12T18:16:52.557
Modified: 2026-05-12T18:16:52.557
Link: CVE-2026-31241
No data.
OpenCVE Enrichment
Updated: 2026-05-12T19:00:20Z