CVE-2026-31241: mem0 server lacks authentication and authorization controls for its memory deletion API endpoint
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., userid, runid, agentid) in the request query parameters.
Published May 12, 2026 · Updated May 27, 2026
Affected packages
mem0ai
- Ecosystem
- PyPI
- Affected
- <= 1.0.0
- Fixed in
- No patched version yet
- Check
pip show mem0ai
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-116575
Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)
medium6.3Oct 28, 2026CVE-2026-115324
mem0ai Databricks vector store vulnerable to SQL injection
critical8.1Oct 22, 2026CVE-2026-31240
mem0 server lacks authentication and authorization controls for its memory management API endpoints
high7.5No fixMay 12, 2026CVE-2026-31245
mem0 server lacks authentication and authorization controls for its memory creation API endpoint
medium5.3No fixMay 12, 2026CVE-2026-7597
mem0ai mem0 has an Improper Input Validation Issue
low6.3May 2, 2026
