CVE-2026-116575

Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)

Published Oct 26, 2026 CVSS 3.1 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Python SDK 2.0.18 or newer.
  • Upgrade to TypeScript SDK 3.1.6 or newer.
  • If an upgrade is not immediately possible, enforce strict validation of user_id, agent_id, and run_id to reject or escape '&' and '=' characters before they reach the SDK.

Generated by OpenCVE AI on October 27, 2026 at 01:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-5324-3w58-qpp2 Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mem0ai
Mem0ai mem0
Vendors & Products Mem0ai
Mem0ai mem0
Type Values Removed Values Added
Description 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.
Title Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)
Weaknesses CWE-200
CWE-863
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 27, 2026, 2:18 PM
Reserved
Oct 26, 2026, 3:03 PM
Status
Deferred
Published
Oct 26, 2026, 9:18 PM
Modified
Oct 27, 2026, 4:04 PM