Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
mem0ai versions before 2.0.0b2 have an input validation flaw in the FAISS vector store that leads to unsafe pickle deserialization. A remote attacker can trigger it by manipulating input, and a public exploit exists. Upgrade to mem0ai 2.0.0b2 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P | CNA (VulDB) |
- CISA KEV Not listed.
- EPSS 0.0032, the 24th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:01 UTC First seen by agentprime
- 31 Oct 2026, 15:01 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-xqxw-r767-67m7
- OSV: GHSA-xqxw-r767-67m7
- nvd.nist.gov/vuln/detail/CVE-2026-7597
- github.com/mem0ai/mem0/issues/3778
- github.com/mem0ai/mem0/pull/4833
- github.com/mem0ai/mem0/commit/62dca096f9236010ca15fea9ba369ba740b86b7a
- github.com/mem0ai/mem0
- vuldb.com/submit/805562
- vuldb.com/vuln/360550
- vuldb.com/vuln/360550/cti