/

CVE-2026-50027

Severity:

CRITICAL RISK

(9.8)

Missing Authentication (CWE-306) in MCP Memory API

CVE-2026-50027

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized Data Access, Modification, and Deletion

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

mcp-memory-service exposes its /api/documents/* HTTP routes without an authentication dependency, even when API-key or OAuth protection is configured. An unauthenticated remote attacker may upload content, read stored documents, or permanently delete memories associated with authenticated users.

Affected context

The vulnerability occurs in deployments of mcp-memory-service where the document-management routes under /api/documents/* are reachable over the network. The configured API key or OAuth controls may protect related /api/memories routes while failing to cover these document endpoints, creating an inconsistent authentication boundary.

Exploit preconditions

  • Attack surface: Network-accessible HTTP endpoints under /api/documents/*
  • Required access: No credentials are required when the vulnerable routes are reachable
  • Trigger point: Requests to document upload, retrieval, or deletion operations
  • Why exploitation is possible: The affected routes do not enforce the authentication dependency applied to protected API functionality

Why this happens

The underlying bug is an inconsistent access-control configuration in which sensitive HTTP routes are registered without an authentication dependency. This allows requests to reach document and memory operations before API-key or OAuth authorization is evaluated. The behavior maps to CWE-306: Missing Authentication for Critical Function, because security-sensitive functionality can be invoked without verifying the caller's identity.

Potential impact

  • An attacker may inject arbitrary content into the semantic memory store
  • An attacker may retrieve documents or other stored content without authorization
  • An attacker may permanently delete memories belonging to authenticated users
  • Stored knowledge may be corrupted, poisoned, or made unavailable
  • Downstream AI applications may produce unreliable or manipulated results

General mitigation guidance

Mitigation generally focuses on making authentication and authorization mandatory for every sensitive route.

Common defensive patterns include:

  • Applying a shared authentication middleware or dependency to all document and memory-management endpoints
  • Enforcing authorization checks consistently at the router and operation levels
  • Using deny-by-default behavior for newly added HTTP routes
  • Treating API keys and OAuth tokens as required controls rather than optional configuration
  • Limiting write and delete permissions through least-privilege roles
  • Separating read, write, and destructive-operation permissions
  • Protecting the service behind network controls while preserving endpoint-level authorization

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and route audits that flag sensitive endpoints without authentication middleware
  • Code review checks comparing security dependencies across related route groups
  • Automated tests that exercise every document and memory operation with missing, invalid, and valid credentials
  • API gateway or policy rules requiring authentication for all state-changing and data-retrieval paths
  • Monitoring for anonymous uploads, reads, and deletion requests
  • Periodic authorization-boundary reviews when new routes or authentication modes are introduced

Sources

SourceLink
github.comgithub.com/advisories/GHSA-84hp-mqvj-3p8h
pypi.orgpypi.org/project/mcp-memory-service
web.archive.orgweb.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service

Frequently asked

questions

Yes. If the affected HTTP routes are network-accessible, an attacker may interact with them remotely without credentials.

No API key, OAuth token, or authenticated account is required for the vulnerable document routes, although network reachability is necessary.

Require authentication and operation-specific authorization on every sensitive route, using a deny-by-default policy and consistent middleware.

Maintain centralized route protection, add automated unauthenticated-access tests, review new endpoints for authorization coverage, and monitor anonymous requests to sensitive operations.

Find out what's already
exploitable in your codebase.