CVE-2026-7597: mem0ai mem0 · Deserialization
Affects mem0ai mem0Source CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:PExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mem0aimem0 | Affected
| Fixed in– |
GitHubmem0ai/mem0pkg:github/mem0ai/mem0Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch identified by commit 62dca096f9236010ca15fea9ba369ba740b86b7a is available and should be applied to all affected versions (1.0.0 through 1.0.11) of mem0ai mem0 to remediate this vulnerability. No alternative mitigations or vendor advisory details are provided, so applying the official patch is the recommended action.
Description
A vulnerability was found in mem0ai mem0 up to 1.0.11. This affects the function pickle.load/pickle.dump of the file mem0/vector_stores/faiss.py. Performing a manipulation results in deserialization. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The patch is named 62dca096f9236010ca15fea9ba369ba740b86b7a. Applying a patch is the recommended action to fix this issue.
References
- vuldb.com/vuln/360550 (opens in a new tab)
- vuldb.com/vuln/360550/cti (opens in a new tab)
- vuldb.com/submit/805562 (opens in a new tab)
- github.com/mem0ai/mem0/issues/3778 (opens in a new tab)
- github.com/mem0ai/mem0/pull/4833 (opens in a new tab)
- github.com/mem0ai/mem0/commit/62dca096f9236010ca15fea9ba369ba740b86b7a (opens in a new tab)
- github.com/mem0ai/mem0/ (opens in a new tab)