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.

No CVSS v4.0

Attack Vector Network

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
doobidoo mcp-memory-service affected
Version Status Constraints
< 10.65.3 affected —

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

Vendors Products
Doobidoo Subscribe
Mcp-memory-service Subscribe

Project Subscriptions

Vendors Products
Doobidoo Subscribe
Mcp-memory-service Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

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

Fri, 19 Jun 2026 20:15:00 +0000

Type Values Removed Values Added
First Time appeared Doobidoo
Doobidoo mcp-memory-service
Vendors & Products Doobidoo
Doobidoo mcp-memory-service

Fri, 19 Jun 2026 18:45:00 +0000

Type Values Removed Values Added
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.
Title mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-06-19T17:59:48.862Z

Reserved: 2026-05-28T20:07:58.862Z

Link: CVE-2026-49291

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-19T20:30:04Z

Weaknesses