MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

security ·

CVE record published for critical unauthenticated document API in mcp-memory-service, whose GitHub repository has since disappeared

CVE-2026-50027 was published to the National Vulnerability Database on 2026-08-14 with a CVSS score of 9.8, covering mcp-memory-service versions before 10.67.1. All HTTP routes under /api/documents/* were served without authentication even when the server was configured with an API key or OAuth, letting an unauthenticated remote attacker write, read, and delete stored memory content. The underlying GitHub advisory was published 2026-07-02. The project's GitHub repository and maintainer account returned 404 when checked on 2026-08-14, while PyPI releases continued through 11.8.0 on 2026-08-09.

A CVE record for mcp-memory-service, a semantic memory MCP server distributed on PyPI, was published to the National Vulnerability Database on 2026-08-14 as CVE-2026-50027, with a CVSS score of 9.8. In versions before 10.67.1, every HTTP route under /api/documents/* was served without any authentication dependency, even when the server was configured with an API key via MCP_API_KEY or with OAuth. An unauthenticated remote attacker could upload arbitrary content into the memory store, retrieve stored document content, and permanently delete memories.

The gap was one-sided: the advisory notes the adjacent /api/memories endpoints enforced authentication correctly. The fix shipped in 10.67.1. The underlying GitHub advisory, GHSA-84hp-mqvj-3p8h, was published to the global advisory database on 2026-07-02, six weeks before the NVD record.

The project's public footprint has changed since the advisory was published. The repository it names, doobidoo/mcp-memory-service, returned HTTP 404 when checked on 2026-08-14, as did the maintainer account itself, and the NVD record cites a web.archive.org snapshot of the repository rather than a live page. Distribution on PyPI has continued: the package's latest release is 11.8.0, uploaded 2026-08-09, and its metadata no longer carries a repository link. No fetched source states why the repository is unavailable.

How was this verified, and what are the sources?

Published · confidence 1.00.

  1. NVD record for CVE-2026-50027 (published 2026-08-14, CVSS 9.8 critical) - 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, retrieve stored document content, and delete memories - accessed
  2. GitHub global advisory GHSA-84hp-mqvj-3p8h (published 2026-07-02, severity critical) - "mcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete"; pip package mcp-memory-service, vulnerable range < 10.67.1, patched in 10.67.1 - accessed
  3. Negative check - https://github.com/doobidoo/mcp-memory-service, the repository named by the advisory, returned HTTP 404 on 2026-08-14; the maintainer account https://github.com/doobidoo also returned 404, and the NVD record's repository reference points at a web.archive.org snapshot - accessed
  4. PyPI JSON metadata for mcp-memory-service - latest release 11.8.0 uploaded 2026-08-09; version 10.67.1 present in the release history; the package metadata carries no repository or homepage link - accessed

← All news