cve.bz

CVE-2026-116575 mem0ai mem0: Incorrect Authorization

6.3 mediumEPSS 0.1%Fix available

Medium (6.3) in mem0ai mem0. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in mem0ai 2.0.18, 3.1.6.

On this page
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.

Severity

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • mem0ai (PyPI): fixed in 2.0.18
  • mem0ai (npm): fixed in 3.1.6

Ask an AI about this CVE

Show the promptExplain CVE-2026-116575 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116575?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116575?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116575 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mem0ai mem0< 2.0.18

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5324-3w58-qpp2PyPImem0ai<2.0.182.0.18
GHSA-5324-3w58-qpp2npmmem0ai<3.1.63.1.6

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON