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