CVE-2026-116575

MEDIUM CVSS 6.3
Published: 2026-10-26
Modified: 2026-10-27
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-116575 is a moderate vulnerability with a CVSS score of 6.3 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

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.

Attack Chain
1
Reconnaissance

Attacker scans for vulnerable versions using version banners or PoC scanners

2
Initial Access

Attacker triggers CVE-2026-116575 vulnerability with a crafted request or payload

3
Execution

Vulnerability exploited to perform unauthorized actions on the target system

4
Impact

Depending on vulnerability type, attacker achieves data access, service disruption, or code execution

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Public-facing application vulnerability exploited for initial access

T1203 Exploitation for Client Execution
Execution

Vulnerability exploited to execute attacker-controlled code

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.