CVE-2026-49291
mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call
Description
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.
INFO
Published Date :
June 19, 2026, 5:59 p.m.
Last Modified :
June 19, 2026, 5:59 p.m.
Remotely Exploit :
No
Source :
GitHub_M
Solution
- Update mcp-memory-service to version 10.65.3 or later.
- Enforce proper OAuth scopes for all requests.
- Validate tool access based on required permissions.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-49291 vulnerability anywhere in the article.