cve.bz

CVE-2026-7597 mem0ai mem0: Deserialization of Untrusted Data

2.1 lowEPSS 0.3%Fix available

Low (2.1) in mem0ai mem0. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in mem0ai 2.0.0b2.

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

Severity

CVSS 4.0

2.1 low
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

CVSS 3.1

6.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-05-04. 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-20 Improper Input Validation
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A05:2025 Injection, A08:2025 Software or Data Integrity Failures
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.0b2

Ask an AI about this CVE

Show the promptExplain CVE-2026-7597 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7597?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7597?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-7597 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 mem01.0.0
mem0ai mem01.0.1
mem0ai mem01.0.2
mem0ai mem01.0.3
mem0ai mem01.0.4
mem0ai mem01.0.5
mem0ai mem01.0.6
mem0ai mem01.0.7
mem0ai mem01.0.8
mem0ai mem01.0.9
mem0ai mem01.0.10
mem0ai mem01.0.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xqxw-r767-67m7PyPImem0ai<2.0.0b22.0.0b2
PYSEC-2026-2636PyPImem0ai<2.0.0b22.0.0b2

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

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

References

Check your stackJSON