CVE-2026-49291: high-severity vulnerability in doobidoo mcp-memory-service
mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call
Published · Updated
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.1epss 0.5%
exploitation probability
0.5%top 60% of all CVEs
observed exploitation
nono source reports it
mcp-memory-service is a semantic memory layer for AI applications. Prior to version 10.65.3, the HTTP MCP JSON-RPC endpoint at `/mcp` requires only OAuth `read` scope for all requests, then dispatches `tools/call` directly to handlers that include mutating tools. A read-only OAuth client can call `store_memory` and `delete_memory` through MCP even though the corresponding REST endpoints require `write` scope. Version 10.65.3 patches the issue.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Affected products
doobidoo · mcp-memory-serviceRelated CVEs — doobidoo mcp-memory-service
In the same product, most dangerous first.
CVE-2026-50027CRITICALmcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/DeleteEPSS 1.0%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%