Vulnerability in mem0ai (CVE-2026-7597)
Summary
Vulnerability in mem0ai (CVE-2026-7597). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.0.0b2 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-7597 has been found in mem0ai.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mem0ai to 2.0.0b2 or later.
If unsure, ask your IT team or search "mem0ai CVE-2026-7597" on the vendor's site.
CVE-2026-7597 (mem0ai) — CWE-20
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.0b2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in mem0ai.
Check the vendor advisory for the affected versions of mem0ai.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.0.0b2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mem0ai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mem0ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mem0aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mem0ai to 2.0.0b2ステージング環境で 2.0.0b2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web vuldb.com
- web vuldb.com
- web vuldb.com