mem0ai mem0 has an Improper Input Validation Issue
CVE-2026-7597 · GHSA-xqxw-r767-67m7 · published 2026-05-02 · updated 2026-05-07
- Severity
- Low
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- 0.32%
- Fixed in
- 2.0.0b2
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade mem0ai to 2.0.0b2 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mem0ai | PyPI | < 2.0.0b2 | 2.0.0b2 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- Highmem0 server lacks authentication and authorization controls for its memory management API endpointsmem0ai
- MediumMem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)mem0ai
- Mediummem0 server lacks authentication and authorization controls for its memory creation API endpointmem0ai
- Mediummem0 server lacks authentication and authorization controls for its memory deletion API endpointmem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.