{"answers":{"affected":"4 open source packages ship an affected version, including mem0ai.","exploited":"There is no known exploitation of CVE-2026-116575 in the wild and no public exploit code.","fix":"Upgrade mem0ai to a fixed version for your release line: 2.0.18 or 3.1.6.","what":"CVE-2026-116575 is a medium-severity vulnerability in mem0ai mem0, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116575 and fix it if it is affected.\n\nWhat it is: CVE-2026-116575 is a medium-severity vulnerability in mem0ai mem0, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116575 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mem0ai (PyPI): affected all versions; fixed in 2.0.18\n- mem0ai (PyPI): affected all versions; fixed in 2.0.18\n- mem0ai (npm): affected all versions; fixed in 3.1.6\n- mem0ai (npm): affected all versions; fixed in 3.1.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-116575/ (Markdown: https://insights.sbomify.com/CVE-2026-116575/index.md)","id":"CVE-2026-116575","markdown":"https://insights.sbomify.com/CVE-2026-116575/index.md","name":"CVE-2026-116575","record":{"aliases":["GHSA-5324-3w58-qpp2"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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 \u0026 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.","ecosystems":["PyPI","npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)","id":"CVE-2026-116575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"systeminformation: Windows command injection in services() through Unicode quotation marks","id":"CVE-2026-116576"},"packages":[{"ecosystem":"PyPI","fixed":["2.0.18"],"introduced":["0"],"last_affected":[],"package":"mem0ai","purl":null,"source":"GHSA-5324-3w58-qpp2"},{"ecosystem":"PyPI","fixed":["2.0.18"],"introduced":["0"],"last_affected":[],"package":"mem0ai","purl":"pkg:pypi/mem0ai","source":"GHSA-5324-3w58-qpp2"},{"ecosystem":"npm","fixed":["3.1.6"],"introduced":["0"],"last_affected":[],"package":"mem0ai","purl":null,"source":"GHSA-5324-3w58-qpp2"},{"ecosystem":"npm","fixed":["3.1.6"],"introduced":["0"],"last_affected":[],"package":"mem0ai","purl":"pkg:npm/mem0ai","source":"GHSA-5324-3w58-qpp2"}],"prev":{"headline":"socket.getaddrinfo() accepts embedded null bytes in host and port","id":"CVE-2026-116566"},"products":["mem0"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-27","vendors":["mem0ai"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116575/"}