CVE-2026-49291

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 v3 8.1 HIGH

8.1^/10

CVSS v3 : HIGH

Vector :

Exploitability : 2.8 / Impact : 5.2

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
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/

Configurations

No configuration.

History

25 Oct 2026, 23:10

Type	Values Removed	Values Added
Summary		(es) mcp-memory-service es una capa de memoria semántica para aplicaciones de IA. Antes de la versión 10.65.3, el endpoint HTTP MCP JSON-RPC en ’/mcp’ requiere solo el ámbito ’read’ de OAuth para todas las solicitudes, luego despacha ’tools/call’ directamente a manejadores que incluyen herramientas mutantes. Un cliente OAuth de solo lectura puede llamar a ’store_memory’ y ’delete_memory’ a través de MCP, aunque los endpoints REST correspondientes requieran el ámbito ’write’. La versión 10.65.3 corrige el problema.

Information

Published : 2026-06-19 19:16

Updated : 2026-10-25 23:10

NVD link : CVE-2026-49291

Mitre link : CVE-2026-49291

CVE.ORG link : CVE-2026-49291

JSON object : View

Products Affected

No product.

CWE

CWE-862

Missing Authorization

{"id": "CVE-2026-49291", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-49291", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-06-22T17:07:36.136160Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 5.2, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "doobidoo", "product": "mcp-memory-service", "versions": [{"status": "affected", "version": "< 10.65.3"}]}]}], "published": "2026-06-19T19:16:36.170", "references": [{"url": "https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-2r68-g678-7qr3", "source": "security-advisories@github.com"}, {"url": "https://pypi.org/project/mcp-memory-service/10.65.3", "source": "security-advisories@github.com"}, {"url": "https://web.archive.org/web/20260508112116/https://github.com/doobidoo/mcp-memory-service/", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "mcp-memory-service es una capa de memoria sem\u00e1ntica para aplicaciones de IA. Antes de la versi\u00f3n 10.65.3, el endpoint HTTP MCP JSON-RPC en \u2019/mcp\u2019 requiere solo el \u00e1mbito \u2019read\u2019 de OAuth para todas las solicitudes, luego despacha \u2019tools/call\u2019 directamente a manejadores que incluyen herramientas mutantes. Un cliente OAuth de solo lectura puede llamar a \u2019store_memory\u2019 y \u2019delete_memory\u2019 a trav\u00e9s de MCP, aunque los endpoints REST correspondientes requieran el \u00e1mbito \u2019write\u2019. La versi\u00f3n 10.65.3 corrige el problema."}], "lastModified": "2026-10-25T23:10:00.167", "sourceIdentifier": "security-advisories@github.com"}