mem0 server lacks authentication and authorization controls for its memory deletion API endpoint
CVE-2026-31241 · GHSA-gq6f-qwv9-rf4j · published 2026-05-12 · updated 2026-05-27
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- 0.39%
- Fixed in
- No fix yet
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
No fixed release is listed yet for mem0ai. Follow the source advisory for updates, and until one ships:
General guidance from ShieldPi, not a vendor fix
- Missing or bypassable authentication. Do not expose it on a network others can reach, and put authentication you control in front of it, such as an authenticating proxy or a VPN. Binding it to localhost is not enough on its own: a web page open in your browser can still reach it, so require a token as well.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mem0ai | PyPI | <= 1.0.0 | No fix yet |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- Highmem0 server lacks authentication and authorization controls for its memory management API endpointsmem0ai
- MediumMem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)mem0ai
- Mediummem0 server lacks authentication and authorization controls for its memory creation API endpointmem0ai
- Lowmem0ai mem0 has an Improper Input Validation Issuemem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.