CVE-2026-50027
Received Received - Intake

Unauthenticated Access in mcp-memory-service

Vulnerability report for CVE-2026-50027, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-14

Last updated on: 2026-08-14

Assigner: GitHub, Inc.

Description

mcp-memory-service is a semantic memory layer for AI applications. Prior to 10.67.1, all HTTP routes under /api/documents/* in mcp-memory-service are served without any authentication dependency, even when the server is configured with an API key (MCP_API_KEY) or OAuth. An unauthenticated remote attacker can upload arbitrary content into the memory store (write), retrieve stored document content (read), and permanently delete memories belonging to authenticated users (delete) β€” all without supplying any credentials. The /api/memories counterpart correctly enforces authentication, making this an inconsistent and exploitable authentication boundary. This vulnerability is fixed in 10.67.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-14
Last Modified
2026-08-14
Generated
2026-08-14
AI Q&A
2026-08-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects mcp-memory-service, a tool for AI applications. Before version 10.67.1, all HTTP routes under /api/documents/* could be accessed without authentication, even if the server was configured with an API key or OAuth. This allowed unauthenticated attackers to upload, read, or delete memories without credentials. The /api/memories endpoint correctly enforced authentication, creating an inconsistent security boundary.

Detection Guidance

Check if the mcp-memory-service is running and verify the version installed. If it is below 10.67.1, the system is vulnerable. Inspect network traffic for requests to /api/documents/* endpoints without authentication headers. Use curl commands to test unauthenticated access to these endpoints, such as: curl http://<server>/api/documents/list or curl -X POST http://<server>/api/documents/upload --data '{"content":"test"}'.

Impact Analysis

An attacker could exploit this to upload malicious content, steal sensitive data from stored memories, or permanently delete memories belonging to users. This could lead to data breaches, loss of critical information, or disruption of AI application functionality.

Compliance Impact

This vulnerability could violate GDPR by exposing personal data without authorization and HIPAA by allowing unauthorized access to protected health information. It undermines data confidentiality and integrity requirements, potentially leading to legal penalties and loss of trust.

Mitigation Strategies

Upgrade mcp-memory-service to version 10.67.1 or later immediately. If upgrading is not possible, restrict network access to the service using firewalls or network policies. Ensure all /api/documents/* endpoints enforce authentication by verifying configuration files and router dependencies in documents.py.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-50027. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart