CVE-2026-50027: fallo crítico en doobidoo mcp-memory-service
mcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete
Publicada el · Actualizada el
28Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 9.8epss 1.0%
probabilidad de explotación
1.0%top 40% de las CVE
explotación observada
noninguna fuente lo reporta
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Productos afectados
doobidoo · mcp-memory-serviceCVEs relacionadas — doobidoo mcp-memory-service
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-49291HIGHmcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/callEPSS 0.5%CVE-2026-33010HIGHmcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory TheftEPSS 0.5%CVE-2026-29787MEDIUMmcp-memory-service: System Information Disclosure via Health EndpointEPSS 0.4%