Mem0 provides persistent memory infrastructure for AI agents and applications. Prior to Python SDK 2.0.18 and TypeScript SDK 3.1.6, _build_session_scope() in mem0/memory/main.py and Memory.buildSessionScope() in the TypeScript SDK join caller-controlled user_id, agent_id, and run_id values using unescaped & and = delimiters. A caller can embed another scope component in a controlled identifier so that distinct tenant tuples produce the same session_scope key. Memory.add(), AsyncMemory.add(), and the REST POST /memories flow use that key to read and save recent raw messages, allowing cross-tenant conversation disclosure and eviction or interleaving of another tenant's history. This issue is fixed in Python SDK 2.0.18 and TypeScript SDK 3.1.6.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusPublished → DeferredNVD modified 2026-10-27 16:04
- StatusReceived → PublishedNVD modified 2026-10-27 14:18
- StatusPublished → ReceivedNVD modified 2026-10-27 15:16
- StatusReceived → PublishedNVD modified 2026-10-26 20:15
- First seenCVSS 6.3NVD modified 2026-10-26 21:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.