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

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 changed around the record's publication, then changed back. The repository the advisory names, doobidoo/mcp-memory-service, returned HTTP 404 when checked on 2026-08-14, as did the maintainer account, and the NVD record cites a web.archive.org snapshot of the repository rather than a live page. PyPI distribution continued through the gap, with 11.8.0 uploaded 2026-08-09 and the package metadata carrying no repository link.

Update, 2026-08-25: the repository and the maintainer account are live again, and the project has explained the arrangement. The v11.8.1 release notes, published on GitHub 2026-08-22, state that development moved to Codeberg at the end of May 2026, that the GitHub repository now operates as a mirror, and that every release from v10.71.0 through v11.8.1 shipped on Codeberg in the interim while PyPI and Docker Hub distribution continued as usual. The PyPI metadata for the current release, 11.8.4, once more links the GitHub repository as its homepage after carrying no repository link when checked on 2026-08-14. What the fetched sources still do not state is why the GitHub repository and account 404'd rather than redirecting during the move. The project has also published a new critical advisory since: an OAuth authorization bypass fixed in v11.8.2, covered separately.