Auth bypass in Mem0ai Mem0
CVE-2026-116575
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.
Vulnerability class: Information Disclosure
Published .
CVSS v3 metric
CVSS v3 base score 6.3 (Medium). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Mem0ai Mem0 — versions < 2.0.18
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-116575?
- CVE-2026-116575 is a medium-severity vulnerability in Mem0ai Mem0, classified under Information Disclosure. CVSS score: 6.3/10. Published 2026-10-26.
- How severe is CVE-2026-116575?
- Medium severity. CVSS v3 base score is 6.3 out of 10.