mcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-306.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| doobidoo | mcp-memory-service | before 10.67.1 | 10.67.1 | Patch available | CNA |
| — | mcp-memory-service (PyPI) | before 10.67.1 | 10.67.1 | Patch available | GHSA-84hp-mqvj-3p8h |
- mcp-memory-service Vendordoobidoo Affected before 10.67.1 Fixed in 10.67.1 Patch available CNA
- mcp-memory-service (PyPI) Vendor— Affected before 10.67.1 Fixed in 10.67.1 Patch available GHSA-84hp-mqvj-3p8h
Remediation
- Fix · CNA mcp-memory-service (doobidoo) Fixed in 10.67.1
- Fix · GHSA-84hp-mqvj-3p8h mcp-memory-service (PyPI) Fixed in 10.67.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-50027
- 2026-10-03 Alias added: GHSA-84hp-mqvj-3p8h
References
Other 5
- https://web.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service
- https://github.com/advisories/GHSA-84hp-mqvj-3p8h
- https://pypi.org/project/mcp-memory-service
- https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-84hp-mqvj-3p8h
- https://github.com/doobidoo/mcp-memory-service
More doobidoo vulnerabilities
- TI-2026-25457 mcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theft CVSS 3.1HIGH 8.8
- TI-2026-23373 mcp-memory-service: System Information Disclosure via Health Endpoint CVSS 3.1MEDIUM 5.3
- TI-2026-36477 mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call CVSS 3.1HIGH 8.1
Sources
- CVE-2026-50027 · CVE Program
- CVE-2026-50027 · NVD
- FIRST EPSS
- GHSA-84hp-mqvj-3p8h · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences