mem0 server lacks authentication and authorization controls for its memory management API endpoints

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-31240: 0.37% estimated exploitation activity in the next 30 days; percentile 31.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The mem0 1.0.0 server lacks authentication and authorization controls for its memory management API endpoints. Critical functions such as updating memory records (PUT /memories/{memoryid}) are exposed without any verification of the requester's identity or permissions. A remote attacker can exploit this by sending unauthenticated requests to modify, overwrite, or delete arbitrary memory records, leading to unauthorized data manipulation and potential data loss.

Published by the source

12 May 2026, 18:30 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jfv9-68m5-gjjr

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jfv9-68m5-gjjr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31240

Advisory: mem0 server lacks authentication and authorization controls for its memory management API endpoints
IDs: CVE-2026-31240, GHSA-jfv9-68m5-gjjr
Record: https://patchnext.com/advisories/cve-2026-31240 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mem0ai: affected <= 1.0.0

## Suggested inspection (read-only)
- `python -m pip show mem0ai`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mem0ai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jfv9-68m5-gjjr (OSV record GHSA-jfv9-68m5-gjjr lists affected ranges: PyPI mem0ai >=0 <=1.0.0)
- Verified: https://github.com/advisories/GHSA-jfv9-68m5-gjjr (GitHub-reviewed advisory GHSA-jfv9-68m5-gjjr lists affected ranges: PyPI mem0ai >=0 <=1.0.0)

Commands are suggestions: review each one before running it.