AAK-MCP-MEMSERVICE-CVE-2026-50027-001: mcp-memory-service below 10.67.1 (/api/documents/* served with no authentication)
- Severity
- CRITICAL
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
McpMemoryServiceUnauthDocuments
What it detects
mcp-memory-service, a semantic memory layer for AI applications, before 10.67.1 serves every HTTP route under /api/documents/* with no authentication dependency attached — even when the server is configured with an API key (MCP_API_KEY) or OAuth. An unauthenticated remote caller can write arbitrary content into the memory store, read stored document content back out, and permanently delete memories belonging to authenticated users. The sibling /api/memories routes do enforce authentication, which is what makes this an inconsistent boundary rather than a server that is simply open: an operator who checks one route reasonably concludes the surface is protected (CVE-2026-50027, CVSS 9.8). Fixed in 10.67.1; GHSA-84hp-mqvj-3p8h records the affected range as < 10.67.1.
How to fix
Upgrade mcp-memory-service to >= 10.67.1 and pin it. Until then treat the memory store as world-writable and world-readable: do not expose the port beyond loopback, and assume any document already in it may have been read or altered. Apply the auth dependency at the router level rather than per-route, so a new route cannot ship unprotected by omission.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-MEMSERVICE-CVE-2026-50027-001
Limitations
Reads mcp-memory-service in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, taking the lowest version a range allows and reporting a reference that states no version. The dependency is not read when it is declared in a sub-directory manifest (services/api/pyproject.toml), in .cursor/mcp.json or .vscode/mcp.json, or in a lockfile format the reader does not parse (pdm.lock). The doobidoo/mcp-memory-service image tag is not read, in a compose file or in an MCP config that starts it with docker run. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-50027
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP07:2025 (Insufficient Authentication & Authorization)
- OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities), ASI06 (Memory & Context Poisoning)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-MEMSERVICE-CVE-2026-50027-001.md: the page then shows that text, with the registry reference appended under it.