mem0ai
6 published advisories; version 2.0.18 or later fixes all but 3 of them.
- Registry
- PyPI
- Advisories
- 6
- Latest fix
- 2.0.18
- Exploited in the wild
- None listed
3 advisories have no fixed release in any version yet. What can be done meanwhile:
General guidance from ShieldPi, not a vendor fix
- Missing or bypassable authentication. Do not expose it on a network others can reach, and put authentication you control in front of it, such as an authenticating proxy or a VPN. Binding it to localhost is not enough on its own: a web page open in your browser can still reach it, so require a token as well.GHSA-cgx8-qgvr-f7vf · GHSA-gq6f-qwv9-rf4j · GHSA-jfv9-68m5-gjjr
Check your projects
shieldpi agent-config checks agent and MCP packages from npm and PyPI, not mem0ai. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.
osv-scanner scan source -r .Or check a lockfile against ShieldMap in your browser.
Source: github.com/mem0ai/mem0, named in the package metadata (not verified)
10 of the last 10 releases of mem0ai were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 2.2.1
- 2.2.0
- 2.1.0
- 2.0.20
- 2.0.19
- 2.0.18
- 2.0.17
- 2.0.16
- 2.0.15
- 2.0.14
Green: published with provenance. Grey: without.
OpenSSF Scorecard has not scored this repository.
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
| Advisory | Severity | Affected | Fixed in | Published |
|---|---|---|---|---|
| Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope)CVE-2026-116575 | Medium | < 2.0.18 | 2.0.18 | 2026-10-28 |
| mem0ai Databricks vector store vulnerable to SQL injectionCVE-2026-115324 | Critical | >= 0.1.117, < 1.0.8 | 1.0.8 | 2026-10-22 |
| mem0 server lacks authentication and authorization controls for its memory creation API endpointCVE-2026-31245 | Medium | <= 1.0.0 | No fix yet | 2026-05-12 |
| mem0 server lacks authentication and authorization controls for its memory deletion API endpointCVE-2026-31241 | Medium | <= 1.0.0 | No fix yet | 2026-05-12 |
| mem0 server lacks authentication and authorization controls for its memory management API endpointsCVE-2026-31240 | High | <= 1.0.0 | No fix yet | 2026-05-12 |
| mem0ai mem0 has an Improper Input Validation IssueCVE-2026-7597 | Low | < 2.0.0b2 | 2.0.0b2 | 2026-05-02 |
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].