CVE-2026-49291

mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call

CVSS 8.1 HIGHEPSS 0.3%CWE-862

Vexday Risk Score

21Low

SSVC decision (CISA)

Track

No exploitation signal → monitor

CVSS 8.1EPSS 0.3%KEV nãoPoC —Nuclei —Metasploit —Patch —

Lifecycle

19 Jun 2026Published on NVD

Recommendation: Monitor — no exploitation signal at the moment.

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-service

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-2r68-g678-7qr3 https://pypi.org/project/mcp-memory-service/10.65.3 https://web.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service/