CVE-2026-59705: mem0 - OpenMemory API Unauthenticated Access via Memory Endpoints

What it is

mem0’s openmemory/api component contains an unauthenticated access vulnerability that allows unauthenticated attackers to read, write, and delete arbitrary user memories by accessing API routers registered without authentication middleware. Attackers can supply arbitrary user_id parameters or directly access memory retrieval endpoints to expose private memory content, or invoke pause endpoints with global_pause=true to cause denial-of-service across all users.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-07-07).

Weakness: Missing Authentication for Critical Function

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 8 references on Exploit Observer

Live scores

EPSS

0.006
low predicted chance of attack

VEDAS

0.986
strong exploit evidence

On CISA KEV

Not listed

Detection rule

Nuclei · Suricata

Who is affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: a3154d5.

Vendor guidance:

• Patch Commit (patch)

How to detect it

Nuclei template (active check)

mem0 OpenMemory - Unauthenticated Memory Access

mem0’s OpenMemory API registers memory routers without authentication middleware, allowing unauthenticated attackers to read, write and delete arbitrary user memories. By supplying an arbitrary user_id to the memory listing endpoint an attacker can enumerate and expose private memory content. This template confirms the flaw non-destructively by listing memories without any credentials.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /api/v1/memories/?user_id={{randstr}}); it decides using status, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

nuclei -u https://your-host -t CVE-2026-59705.yaml

id: CVE-2026-59705

info:
  name: "mem0 OpenMemory - Unauthenticated Memory Access"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    mem0's OpenMemory API registers memory routers without authentication middleware, allowing
    unauthenticated attackers to read, write and delete arbitrary user memories. By supplying an
    arbitrary user_id to the memory listing endpoint an attacker can enumerate and expose private
    memory content. This template confirms the flaw non-destructively by listing memories without
    any credentials.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-59705&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=mem0&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2026-59705
    cwe-id: CWE-306
  metadata:
    verified: false
    max-request: 1
  tags: cve,cve2026,mem0,openmemory,missing-auth,unauth

http:
  - method: GET
    path:
      - "{{BaseURL}}/api/v1/memories/?user_id={{randstr}}"
    headers:
      Accept: application/json
    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - '"items"'
          - '"total"'
          - '"page"'
        condition: and
      - type: word
        part: header
        words:
          - "application/json"
      - type: status
        status:
          - 200

CVE-2026-59705.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-59705 mem0 OpenMemory - Unauthenticated Memory Access Attempt. Add them to your Suricata rule set and reload.

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-59705 mem0 OpenMemory - Unauthenticated Memory Access Attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/api/v1/memories"; fast_pattern; nocase; content:"user_id"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-59705; reference:url,https://www.exploit.observer/?keyword=CVE-2026-59705&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=mem0&match=exact; sid:1081604; rev:1;)

CVE-2026-59705.rules on GitHub

References

Vendor advisories and patches

• Patch Commit (patch)

Technical analysis and advisories

• GitHub Issue (issue-tracking)
• https://www.vulncheck.com/advisories/mem0-openmemory-api-unauthenticated-access-via-memory-endpoints (third-party-advisory)

Other references

• Product (product)

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.