Skip to content

[GHSA-jfv9-68m5-gjjr] mem0 server lacks authentication and authorization controls for its memory management API endpoints - #8930

Open
donny-devops wants to merge 1 commit into
donny-devops/advisory-improvement-8930from
donny-devops-GHSA-jfv9-68m5-gjjr
Open

[GHSA-jfv9-68m5-gjjr] mem0 server lacks authentication and authorization controls for its memory management API endpoints#8930
donny-devops wants to merge 1 commit into
donny-devops/advisory-improvement-8930from
donny-devops-GHSA-jfv9-68m5-gjjr

Conversation

@donny-devops

Copy link
Copy Markdown

Updates

  • Affected products
  • Description

Comments
Advisory Improvement · mem0 server lacks authentication and authorization controls for its memory management API endpoints

Copilot AI review requested due to automatic review settings August 1, 2026 03:58
@github-actions
github-actions Bot changed the base branch from main to donny-devops/advisory-improvement-8930 August 1, 2026 03:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Expands the mem0 security advisory with detailed impact and remediation information.

Changes:

  • Adds severity, technical details, affected versions, PoC, and remediation.
  • Updates the advisory modification timestamp.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

],
"summary": "mem0 server lacks authentication and authorization controls for its memory management API endpoints",
"details": "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/{memory_id}) 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.",
"details": "The mem0 server in version 1.0.0 exposes critical memory‑management API endpoints without authentication or authorization. Endpoints such as PUT /memories/{memory_id} allow any remote user to modify, overwrite, or delete memory records without verifying identity or permissions. This results in unauthorized data manipulation and potential data loss.\n\nSeverity\nHigh (CVSS 7.5) \nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N\n\nThis vulnerability allows remote, unauthenticated modification of stored data. No privileges or user interaction are required.\n\nTechnical Details\nThe mem0 server’s memory‑management endpoints lack authentication middleware. Requests to endpoints such as:\n\nPUT /memories/{memory_id}\n\nDELETE /memories/{memory_id}\n\nare processed without verifying the requester’s identity. This allows arbitrary modification or deletion of memory records. The issue corresponds to CWE‑306: Missing Authentication for Critical Function.\n\nProof‑of‑Concept (Safe)\nA remote attacker can send an unauthenticated HTTP request:\n\nCode\nPUT /memories/123\nContent-Type: application/json\n\n{\n \"text\": \"attacker-modified content\"\n}\nThe server accepts the request and overwrites the memory record, demonstrating the lack of authentication and authorization.\n\nAffected Versions\nmem0ai (pip) ≤ 1.0.0 \n\nPatched Version\nNone currently available.\n\nRemediation\nImplement authentication and authorization controls for all memory‑management endpoints. Require valid tokens for all state‑changing operations and enforce ownership checks. Release a patched version with secure middleware and proper access control.",
],
"summary": "mem0 server lacks authentication and authorization controls for its memory management API endpoints",
"details": "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/{memory_id}) 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.",
"details": "The mem0 server in version 1.0.0 exposes critical memory‑management API endpoints without authentication or authorization. Endpoints such as PUT /memories/{memory_id} allow any remote user to modify, overwrite, or delete memory records without verifying identity or permissions. This results in unauthorized data manipulation and potential data loss.\n\nSeverity\nHigh (CVSS 7.5) \nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N\n\nThis vulnerability allows remote, unauthenticated modification of stored data. No privileges or user interaction are required.\n\nTechnical Details\nThe mem0 server’s memory‑management endpoints lack authentication middleware. Requests to endpoints such as:\n\nPUT /memories/{memory_id}\n\nDELETE /memories/{memory_id}\n\nare processed without verifying the requester’s identity. This allows arbitrary modification or deletion of memory records. The issue corresponds to CWE‑306: Missing Authentication for Critical Function.\n\nProof‑of‑Concept (Safe)\nA remote attacker can send an unauthenticated HTTP request:\n\nCode\nPUT /memories/123\nContent-Type: application/json\n\n{\n \"text\": \"attacker-modified content\"\n}\nThe server accepts the request and overwrites the memory record, demonstrating the lack of authentication and authorization.\n\nAffected Versions\nmem0ai (pip) ≤ 1.0.0 \n\nPatched Version\nNone currently available.\n\nRemediation\nImplement authentication and authorization controls for all memory‑management endpoints. Require valid tokens for all state‑changing operations and enforce ownership checks. Release a patched version with secure middleware and proper access control.",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants