# CVE-2026-59705 — mem0

> As of 2026-07-07, CVE-2026-59705 is a CRITICAL-severity vulnerability in mem0, CVSS v3.1 9.8. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-59705 as of 2026-07-07; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-07

## What is CVE-2026-59705?

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.

The record classifies CVE-2026-59705 under weakness class [CWE-306](https://intel.threadlinqs.com/cwe/CWE-306). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 90 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 9.8 — CRITICAL (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **CVSS v4.0 base score:** 9.3 (`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`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-07

## Is CVE-2026-59705 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **mem0**: mem0

## How to fix CVE-2026-59705

No vendor patch reference has been recorded for CVE-2026-59705 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-59705

No threat campaign in the Threadlinqs corpus currently references CVE-2026-59705, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-07-09. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/mem0ai/mem0/commit/a3154d59e52386d4e1189c1f5f44819868f76514)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/mem0-openmemory-api-unauthenticated-access-via-memory-endpoints)

**Issue tracking and product pages**

- [github.com — issue tracking](https://github.com/mem0ai/mem0/issues/6080)
- [github.com — product](https://github.com/mem0ai/mem0)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-59705
Full detection coverage and IOCs for threats exploiting CVE-2026-59705 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp