Evidence · DiggingBeagle record
Mem0 agent memory session identifier collision, CVE-2026-116575
Security advisory describing delimiter collisions in concatenated agent, run and user identifiers.
- Source role
- primary disclosure
Evidence record
Security advisory describing delimiter collisions in concatenated agent, run and user identifiers.
Claim-level citations (2)
- supportsMem0 conversation keys could collide across agent, run and user scopes: Mem0 used unescaped ampersands and equals signs when joining agent, run and user identity fields into a conversation-history key, permitting two otherwise different tuples to address the same stored messages.
GHSA-5324-3w58-qpp2: collision example, session assembly, impact and fixed versions
- supportsMem0 conversation keys could collide across agent, run and user scopes: Mem0 combined agent, run and user identifiers with unescaped delimiter characters, allowing differently structured identities to produce the same underlying memory key. The caller must be able to control identifiers containing delimiter syntax; an ordinary account cannot automatically read every other user’s memory. Colliding keys could mix recent messages into an extraction model and permit cross-principal memory reads, writes or eviction.
GHSA-5324-3w58-qpp2: collision example, session assembly, impact and fixed versions