Back to CVE records
High 8.1Published Jun 19, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects doobidoo mcp-memory-service. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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
8.1 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Weakness (CWE)
CWE-862
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Deferred
Record last updated
Jun 22, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
doobidoo mcp-memory-service
doobidoo:mcp_memory_service (from the name)
before 10.65.3
CNA record

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.