Quick answers
- Is CVE-2026-31240 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-31240 being exploited in the wild.
- How severe is CVE-2026-31240?
- High severity, with a CVSS score of 7.5, published 12 May 2026.
- Which products and versions are affected?
- Mem0ai Mem0 1.0.0; mem0ai (PyPI) <= 1.0.0, ECOSYSTEM:introduced=0,last_affected=1.0.0.
- Is there a fix for CVE-2026-31240?
- 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-31240 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-31240?
- Check whether you run Mem0ai Mem0 or 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) is vulnerable to a missing authentication check (CWE-306) for critical memory management API endpoints. Specifically, functions such as 'PUT /memories/{memory_id}' are exposed without any verification of the requester's identity or authorization level. A remote, unauthenticated attacker can exploit this by sending crafted HTTP requests to the network-reachable server to modify, overwrite, or delete arbitrary memory records. This results in a complete loss of integrity for the stored data. As of the advisory date, no patched version has been identified.
Affected products
- mem0ai mem0ai (mem0) <= 1.0.0
Identifiers
- CVE-2026-31240
- GHSA-jfv9-68m5-gjjr
- PYSEC-2026-2635
Timeline
- 2026-05-12: disclosed: Initial disclosure and NVD publication
- 2026-05-12: advisory: GitHub Advisory published