For your digest
mem0ai: Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- mem0ai (PyPI): every version, before 2.0.18
- mem0ai (npm): every version, before 3.1.6
The fix
mem0ai (PyPI) fixed in 2.0.18
pippython -m pip install mem0ai==2.0.18uvuv add mem0ai==2.0.18poetrypoetry add mem0ai@2.0.18Check what is installedpython -m pip show mem0aiPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency mem0ai to 2.0.18 or the nearest later release, to fix CVE-2026-116575. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.mem0ai (npm) fixed in 3.1.6
npmnpm install mem0ai@3.1.6pnpmpnpm add mem0ai@3.1.6yarnyarn add mem0ai@3.1.6bunbun add mem0ai@3.1.6Check what is installednpm ls mem0aiPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency mem0ai to 3.1.6 or the nearest later release, to fix CVE-2026-116575. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".