Summary
CVE-2026-59705 is a critical missing authentication vulnerability (CWE-306) in mem0’s OpenMemory API component (openmemory/api), carrying a CVSS v3.1 score of 9.8 (Critical). The flaw allows unauthenticated network attackers to read, modify, and delete any user’s private AI memories, or trigger a global denial-of-service condition affecting all users of a deployment. All versions of the OpenMemory API prior to patch commit a3154d5 are affected.
Technical details
- Root cause: API routers in
openmemory/api/main.pywere registered without any authentication middleware, and endpoint handlers perform no ownership verification on caller-supplieduser_idparameters — classified as CWE-306 (Missing Authentication for Critical Function). - Trigger conditions: Any HTTP request to the exposed API — no credentials, prior access, or special preconditions are required.
- Attack vector: Network-accessible (AV:N); no authentication required (PR:N), no user interaction (UI:N), low attack complexity (AC:L).
- Confidentiality impact: Unauthenticated attackers can supply arbitrary
user_idvalues or directly invokeGET /api/v1/memories/{memory_id}to retrieve the full private memory content of any user stored in the instance. - Integrity impact: Attackers can create, overwrite, or delete any user’s memories without restriction, corrupting the AI memory layer across the entire deployment.
- Availability impact: Invoking the pause endpoint with
global_pause=truedisables the service simultaneously for all users, resulting in a complete denial of service.
Affected software
- mem0 OpenMemory API (
openmemory/api) — all versions prior to patch commita3154d59e52386d4e1189c1f5f44819868f76514
Severity
CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Patch: Apply the fix introduced at commit
a3154d5, which implements authentication middleware on the previously unprotected API routers. - Project sunset notice: The mem0 maintainer confirmed on July 6, 2026 that the OpenMemory component has been sunset and will receive no further updates. Organizations relying on this component should treat it as end-of-life with no future security support.
- Network isolation (immediate): If patching is not immediately feasible, restrict all inbound internet access to OpenMemory API instances using firewall rules or network segmentation. The service should not be reachable from untrusted networks under any circumstances.
- Reverse proxy authentication: If the API must remain accessible to internal consumers, place it behind an authenticating reverse proxy (enforcing API key, JWT, or session token validation) to block unauthenticated requests at the network boundary.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

