mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call
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 |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Doobidoo | Mcp-memory-service |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2r68-g678-7qr3 | mcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/call |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.488% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Doobidoo
Doobidoo mcp-memory-service |
|
| Vendors & Products |
Doobidoo
Doobidoo mcp-memory-service |
| 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
|