Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)
CVE-2026-116575 · GHSA-5324-3w58-qpp2 · published 2026-10-28
- Severity
- Medium
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- 0.11%
- Fixed in
- 2.0.18
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
Summary buildsessionscope() in mem0/memory/main.py builds the conversation-history scope key used to fetch/store the last N raw messages by naively joining caller-supplied userid/agentid/runid values with unescaped & and = delimiters: def buildsessionscope(filters): validateandtrimentityid() (the only validation applied to these values) rejects only empty/whitespace-only strings — it never forbids & or =. This scope string is then used as an exact-match key against a SQLite column (storage.py: WHERE sessionscope = ?) to fetch the last 10 raw messages for a given scope (main.py, Phase 0 of addtovectorstore, both sync and async).
Upgrade mem0ai to 2.0.18 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mem0ai | PyPI | < 2.0.18 | 2.0.18 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- Highmem0 server lacks authentication and authorization controls for its memory management API endpointsmem0ai
- Mediummem0 server lacks authentication and authorization controls for its memory creation API endpointmem0ai
- Mediummem0 server lacks authentication and authorization controls for its memory deletion API endpointmem0ai
- Lowmem0ai mem0 has an Improper Input Validation Issuemem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.