# CVE-2026-31241: mem0 server missing authentication in memory deletion API

Source: https://junglewise.ai/threats/cve-2026-31241-mem0-server-missing-authentication-in-memory-deletion-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-12. Updated: 2026-05-27  
License: CC BY 4.0 with a link back

CVE-2026-31241 · Severity: medium · CVSS 6.5 · Published 2026-05-12

The mem0 server, which provides a memory layer for AI agents, contains a security flaw in its data deletion interface. An unauthorized person can remotely delete stored memory records belonging to any user without needing a password or account. This could lead to permanent loss of AI training data and disrupt the functionality of AI agents relying on that memory.

Technologies: [mem0ai (PyPI)](https://junglewise.ai/threats/technologies/mem0ai). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-31241 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-31241 being exploited in the wild.

**How severe is CVE-2026-31241?** Medium severity, with a CVSS score of 6.5, published 12 May 2026.

**Which products and versions are affected?** mem0ai (PyPI) <= 1.0.0, ECOSYSTEM:introduced=0,last_affected=1.0.0.

**Is there a fix for CVE-2026-31241?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-31241 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-31241?** Check whether you run mem0ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The mem0 server (version 1.0.0 and earlier) fails to implement authentication (CWE-306) and authorization (CWE-862) on the 'DELETE /memories' API endpoint. An attacker can send unauthenticated HTTP DELETE requests to this endpoint and specify arbitrary identifiers such as 'user_id', 'run_id', or 'agent_id' in the query parameters. Because the server does not verify the identity or permissions of the requester, it will execute the deletion for the specified records. This allows for unauthorized data modification and a denial-of-service condition by purging the memory layer used by AI agents. As of the advisory date, no patched version has been identified.

## Affected products

- mem0ai mem0ai <= 1.0.0

## Identifiers

- CVE-2026-31241
- GHSA-gq6f-qwv9-rf4j
- PYSEC-2026-2634

## Timeline

- 2026-05-12: disclosed: NVD Published Date
- 2026-05-12: advisory: GitHub Advisory published

## References

- [https://github.com/mem0ai/mem0](https://github.com/mem0ai/mem0)
- [https://www.notion.so/CVE-2026-31241-35d1e139318881459ae5e6f0d7dc6f0f](https://www.notion.so/CVE-2026-31241-35d1e139318881459ae5e6f0d7dc6f0f)

## Related threats

- [Mem0 session scope key injection vulnerability](https://junglewise.ai/threats/cve-2026-116575-mem0-provides-persistent-memory-infrastructure-for-ai-agents-and)
- [mem0 SQL injection in Databricks vector store](https://junglewise.ai/threats/cve-2026-115324-mem0-0-1-117-before-1-0-8-contains-an-sql-injection)
- [mem0ai mem0 missing authentication in memory creation API](https://junglewise.ai/threats/cve-2026-31245-mem0ai-mem0-missing-authentication-in-memory-creation-api)
- [mem0ai mem0 missing authentication in memory management API](https://junglewise.ai/threats/cve-2026-31240-mem0ai-mem0-missing-authentication-in-memory-management-api)
- [PYSEC-2026-2636 - mem0ai mem0 has an Improper Input Validation Issue](https://junglewise.ai/threats/cve-2026-7597-mem0ai-mem0-has-an-improper-input-validation-issue)