CVE-2026-116575: falha de média gravidade em mem0ai mem0
Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)
Publicada em · Atualizada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
13Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 6.3epss 0.1%
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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Produtos afetados
mem0ai · mem0CVEs relacionadas — mem0ai mem0
No mesmo produto, das mais perigosas para as menos.
Referências
https://github.com/mem0ai/mem0/commit/71f2ebefa3494da21550fb525216818776cde67fhttps://github.com/mem0ai/mem0/pull/6892https://github.com/mem0ai/mem0/releases/tag/ts-v3.1.6https://github.com/mem0ai/mem0/releases/tag/v2.0.18https://github.com/mem0ai/mem0/security/advisories/GHSA-5324-3w58-qpp2