# CVE-2026-31241: mem0 server lacks authentication and authorization controls for its memory deletion API endpoint

> Unauthenticated attackers can delete memory records for any user via the DELETE /memories endpoint, causing data loss and denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-gq6f-qwv9-rf4j, PYSEC-2026-2634

## What is CVE-2026-31241?

CVE-2026-31241 is a medium-severity missing authorization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service.

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

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

3 open source packages ship an affected version, including mem0ai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mem0ai` | PyPI | All versions to 1.0.0 | None |
| `mem0ai` | PyPI | All versions to 1.0.0 | None |
| `mem0ai` | PyPI | All versions to 1.0.0 | None |

Products: Mem0 Mem0.

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

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

## Is CVE-2026-31241 being exploited?

There is no known exploitation of CVE-2026-31241 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-31242](https://insights.sbomify.com/CVE-2026-31242/): Missing authorization in n/a (critical 9.1)
- [CVE-2026-31243](https://insights.sbomify.com/CVE-2026-31243/): Missing authorization in n/a (medium 6.5)
- [CVE-2026-31244](https://insights.sbomify.com/CVE-2026-31244/): Missing authorization in n/a (medium 6.5)
- [CVE-2026-31245](https://insights.sbomify.com/CVE-2026-31245/): mem0 server lacks authentication and authorization controls for its memory creation API endpoint (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31241 is a medium-severity missing authorization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31241 in the wild and no public exploit code.

Affected packages and fixed versions:
- mem0ai (PyPI): affected all versions up to 1.0.0; no fix listed
- mem0ai (PyPI): affected all versions up to 1.0.0; no fix listed
- mem0ai (PyPI): affected all versions up to 1.0.0; no fix listed

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-31241/ (Markdown: https://insights.sbomify.com/CVE-2026-31241/index.md)
```

## Sources

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

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