Technical impact
Mem0 builds a session‑scope key by concatenating caller‑controlled user_id, agent_id and run_id with unescaped & and = delimiters. In Python SDKs prior to 2.0.18 and TypeScript SDKs prior to 3.1.6, an attacker can embed delimiter characters in any identifier component, causing distinct tenant tuples to generate an identical session_scope key. The key is used by Memory.add, AsyncMemory.add and the REST POST /memories endpoint to read and store recent raw messages. Consequently, a malicious or compromised user can read or interleave another tenant’s conversation history, or evict that tenant’s stored data, undermining confidentiality and integrity.
Affected Systems
The flaw affects mem0’s Python SDK up to version 2.0.17 inclusive and the TypeScript SDK up to version 3.1.5 inclusive. Any deployment that utilizes these SDKs and has not applied the patch delivered in Python SDK 2.0.18 or TypeScript SDK 3.1.6 is vulnerable.
Risk and Exploitability
The CVSS score of 6.3 indicates medium severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog, so no known exploitation has been reported. The attack requires the ability to supply user_id, agent_id or run_id values, which is available to any authenticated user of Mem0. The overall risk is moderate: a compromised or malicious tenant can engineer identifier collisions to read or manipulate another tenant’s conversation data.
Github GHSA