Which versions of mem0 OpenMemory are affected by CVE-2026-59705?

mem0's OpenMemory API server allows unauthenticated remote attackers to read, modify, or delete any user's stored memories and trigger service-wide outages through unprotected API routers.. A patch is available.

How to fix or mitigate CVE-2026-59705?

24 hours: Identify all mem0 OpenMemory API deployments; obtain and apply available vendor patch to openmemory/api component across all instances. 7 days: Verify patch deployment; audit application logs for exploitation attempts (unauthenticated memory access calls, user_id tampering); confirm all API routers enforce authentication middleware. 30 days: Implement API gateway-level authentication validation; deploy monitoring for anomalous memory access patterns; establish quarterly access control audits for API security.

mem0 OpenMemory CVE-2026-59705

Q: What is the CVSS score of CVE-2026-59705?

CVE-2026-59705 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.5%.

EUVD-2026-42126 CRITICAL

Missing Authentication for Critical Function (CWE-306)

2026-07-07 VulnCheck

GHSA-xgj7-grxr-prrp

Authentication Bypass Mem0

9.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.8 CRITICAL

Missing authentication on network-reachable endpoints gives AV:N/AC:L/PR:N/UI:N; arbitrary read/write/delete and global pause yield C:H/I:H/A:H with unchanged scope.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 07, 2026 - 23:20 vuln.today

DescriptionCVE.org

mem0's openmemory/api component contains an unauthenticated access vulnerability that allows unauthenticated attackers to read, write, and delete arbitrary user memories by accessing API routers registered without authentication middleware. Attackers can supply arbitrary user_id parameters or directly access memory retrieval endpoints to expose private memory content, or invoke pause endpoints with global_pause=true to cause denial-of-service across all users.

AnalysisAI

Unauthenticated data theft, tampering, and denial-of-service affects mem0's OpenMemory API server (openmemory/api component), where several API routers are mounted without any authentication middleware. Because CVSS 4.0 vector shows PR:N and CWE-306 (Missing Authentication for a Critical Function), remote attackers can pass arbitrary user_id values to read, overwrite, or delete any user's stored memories, and can trigger a global pause to break the service for everyone. Reported by VulnCheck with a vendor patch commit available; no public exploit identified at time of analysis and not listed in CISA KEV.

Technical ContextAI

mem0 is an open-source long-term memory layer for LLM/AI-agent applications, and OpenMemory is its self-hostable server exposing a FastAPI-style REST API (openmemory/api) for storing and retrieving per-user 'memories'. The root cause is CWE-306, Missing Authentication for a Critical Function: memory CRUD endpoints and control endpoints (e.g. pause) are registered on the app without an auth dependency/middleware, so tenant isolation is enforced only by a client-supplied user_id parameter rather than a verified identity. The single affected CPE, cpe:2.3:a:mem0:mem0, indicates the flaw lives in the mem0 project itself rather than a downstream integration, and because memories often contain sensitive conversational context, ungated access exposes private data across all tenants of a shared instance.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - apply the vendor fix from commit https://github.com/mem0ai/mem0/commit/a3154d59e52386d4e1189c1f5f44819868f76514 by upgrading to a build that includes it and consult https://github.com/mem0ai/mem0/issues/6080 and the VulnCheck advisory (https://www.vulncheck.com/advisories/mem0-openmemory-api-unauthenticated-access-via-memory-endpoints) to confirm the exact release tag. Until patched, do not expose the OpenMemory API to untrusted networks: bind it to localhost or place it behind an authenticating reverse proxy or API gateway that enforces identity and rejects client-controlled user_id spoofing, and restrict network access to the memory and pause endpoints via firewall/allowlist. Specifically disable or block the global pause endpoint (global_pause=true) from external reach to prevent the denial-of-service path; the trade-off of these controls is added deployment complexity and that a proxy-based auth layer must itself map authenticated identity to user_id rather than trusting the request parameter.