# CVE-2026-59705: mem0 - OpenMemory API Unauthenticated Access via Memory Endpoints

> Unauthenticated attackers can read, modify, or delete user memories and cause denial of service in mem0's OpenMemory API due to missing authentication middleware.

- **Severity:** Critical 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-xgj7-grxr-prrp

## What is CVE-2026-59705?

CVE-2026-59705 is a critical missing authorization vulnerability in mem0, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-59705?


## How do I fix CVE-2026-59705?

No fix has been published for CVE-2026-59705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59705 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59705 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59705 and fix it if it is affected.

What it is: CVE-2026-59705 is a critical missing authorization vulnerability in mem0, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59705 exists.

Affected product: mem0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59705/ (Markdown: https://insights.sbomify.com/CVE-2026-59705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59705
- OSV: https://osv.dev/vulnerability/CVE-2026-59705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59705/
Summaries are generated and may contain mistakes; the official description above is the record.