CVE-2026-50027
mcp-memory-service is a semantic memory layer for AI applications. …
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-84hp-mqvj-3p8h
- github.com/advisories/GHSA-84hp-mqvj-3p8h
- pypi.org/project/mcp-memory-service
- web.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service
- nvd.nist.gov/vuln/detail/CVE-2026-50027
- cve.org/CVERecord?id=CVE-2026-50027
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.