CVE-2026-7597

MEDIUMNVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 5, 2026

Advisory Details (4)

Auto-updated May 1, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

fix: prevent arbitrary code execution via pickle in FAISS vector store by kartik-mem0 · Pull Request #4833 · mem0ai/mem0 · GitHub

https://github.com/mem0ai/mem0/pull/4833
generic🟡 PoC Available

[Security] Code Execution via unsafe deserialization · Issue #3778 · mem0ai/mem0 · GitHub

https://github.com/mem0ai/mem0/issues/3778
generic

fix: prevent arbitrary code execution via pickle in FAISS vector store · mem0ai/mem0@62dca09 · GitHub

https://github.com/mem0ai/mem0/commit/62dca096f9236010ca15fea9ba369ba740b86b7a
generic

GitHub - mem0ai/mem0: Universal memory layer for AI Agents · GitHub

https://github.com/mem0ai/mem0/

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mem0ai0.0.1 ... 2.0.0b1 (168 versions)2.0.0b2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-11 18:23 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-30 19:18 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:42 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:47 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 14:18 UTCEPSS rescore
  21. 2026-08-23 21:43 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:56 UTCEPSS rescore
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:49 UTCEPSS rescore
  2. 2026-08-18 13:49 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 13:18 UTCEG score recompute
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 05:14 UTCEG score recompute
  8. 2026-08-16 02:15 UTCEPSS rescore
  9. 2026-08-15 01:31 UTCEPSS rescore
  10. 2026-08-14 03:42 UTCEG score recompute
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 18:11 UTCEG score recompute
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 16:14 UTCEG score recompute
  15. 2026-08-11 13:43 UTCEPSS rescore
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 07:57 UTCEG score recompute
  18. 2026-08-09 13:47 UTCEPSS rescore
  19. 2026-08-09 06:07 UTCEG score recompute
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 04:17 UTCEG score recompute
  22. 2026-08-07 02:26 UTCEG score recompute
  23. 2026-08-06 13:47 UTCEPSS rescore
  24. 2026-08-05 22:34 UTCEG score recompute
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:39 UTCEPSS rescore
  29. 2026-08-03 20:16 UTCEG score recompute
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 05:36 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 04:16 UTCEPSS rescore
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-28 15:37 UTCEPSS rescore
  37. 2026-07-27 14:14 UTCEPSS rescore
  38. 2026-07-26 14:54 UTCEPSS rescore
  39. 2026-07-25 14:18 UTCEPSS rescore
  40. 2026-07-24 14:18 UTCEPSS rescore
  41. 2026-07-23 14:18 UTCEPSS rescore
  42. 2026-07-23 03:22 UTCEG score recompute
  43. 2026-07-22 14:08 UTCEPSS rescore
  44. 2026-07-22 14:08 UTCEPSS rescore
  45. 2026-07-21 15:25 UTCEPSS rescore
  46. 2026-07-21 15:25 UTCEPSS rescore
  47. 2026-07-20 17:08 UTCEPSS rescore
  48. 2026-07-19 18:48 UTCOSV refresh
  49. 2026-07-19 14:31 UTCEPSS rescore
  50. 2026-07-19 02:29 UTCEPSS rescore
  51. 2026-07-18 10:04 UTCEPSS rescore
  52. 2026-07-16 17:03 UTCEPSS rescore
  53. 2026-07-15 16:57 UTCEPSS rescore
  54. 2026-07-15 02:00 UTCEPSS rescore
  55. 2026-07-13 22:31 UTCEPSS rescore
  56. 2026-07-13 06:13 UTCEPSS rescore
  57. 2026-07-12 05:46 UTCEPSS rescore
  58. 2026-07-11 08:27 UTCEPSS rescore
  59. 2026-07-09 19:10 UTCEPSS rescore
  60. 2026-07-09 19:10 UTCEPSS rescore
  61. 2026-07-08 15:16 UTCEPSS rescore
  62. 2026-07-08 15:16 UTCEPSS rescore
  63. 2026-07-06 16:27 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-06 02:23 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-05 02:31 UTCEPSS rescore
  68. 2026-07-05 02:30 UTCEPSS rescore
  69. 2026-07-04 06:31 UTCEPSS rescore
  70. 2026-07-04 06:31 UTCEPSS rescore
  71. 2026-07-01 15:07 UTCEPSS rescore
  72. 2026-06-30 23:22 UTCEPSS rescore
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 04:56 UTCEPSS rescore
  75. 2026-06-27 03:08 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7597?
CVE-2026-7597 is a medium vulnerability published on May 1, 2026. 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.…
When was CVE-2026-7597 disclosed?
CVE-2026-7597 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7597 actively exploited?
CVE-2026-7597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.7% of all scored CVEs.
What is the CVSS score of CVE-2026-7597?
CVE-2026-7597 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-7597?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7597, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7597

Explore →

Is Your Infrastructure Affected by CVE-2026-7597?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs