CVE-2026-49291 is a high-severity missing authorization vulnerability in mcp-memory-service (pip), affecting versions <= 10.65.1. It is fixed in 10.65.3.
Summary 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 storememory and deletememory through MCP even though the corresponding REST endpoints require write scope. Technical Details src/mcpmemoryservice/web/api/mcp.py declares mcpendpoint with user: AuthenticationResult = Depends(requirereadaccess). For tools/call, it extracts the requested tool name and arguments, then calls handletoolcall(storage, toolname, arguments) without passing the authenticated user or checking a per-tool required scope. The MCP tool registry includes both read tools and write tools. In the same handler file, storememory creates a Memory object and calls storage.store(...), while deletememory calls storage.delete(contenthash). These operations are reachable with only the read scope. The REST endpoint demonstrates the intended boundary: POST /api/memories uses Depends(requirewriteaccess) and rejects a read-only token with 403 insufficientscope. Reproduction Enable OAuth and disable anonymous access. Generate a valid OAuth JWT with only scope: read. Confirm the REST write endpoint rejects it: Expected and observed: HTTP 403 with Required scope 'write' not granted. Send the same read-only token to the MCP endpoint: Observed: HTTP 200 JSON-RPC success and the storage store sink is reached. A read-only token can also call deletememory through MCP if it knows a content hash: Observed: HTTP 200 JSON-RPC success and the storage delete sink is reached. Impact A client intended to be read-only can inject or delete memories through the MCP API. This can corrupt the memory database, influence future agent context, and destroy stored user memories without the OAuth write scope required by the REST API. Affected Versions Confirmed present on current main commit c99a922477df41f75a44db11182ae48a57311910 and latest release tag v10.65.0 (4eb4a62665589f9dd9f8c393afa32de434b4098a). Suggested Fix Enforce authorization per MCP tool at tools/call time. Require write for storememory and delete_memory, keep read only for read-only tools, and add regression tests proving direct tools/call to mutating tools is rejected before the handler reaches storage when the caller has only read scope.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
CVE-2026-49291 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (10.65.3). Upgrading removes the vulnerable code path.
pip
mcp-memory-service (<= 10.65.1)mcp-memory-service → 10.65.3 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-49291 is reachable in your applications. Explore AI application security for your team.
See if CVE-2026-49291 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-49291 in your environment →Upgrade mcp-memory-service to 10.65.3 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-49291 is a high-severity missing authorization vulnerability in mcp-memory-service (pip), affecting versions <= 10.65.1. It is fixed in 10.65.3. The application does not perform an authorization check before performing a sensitive operation.
CVE-2026-49291 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
mcp-memory-service (pip) versions <= 10.65.1 is affected.
Yes. CVE-2026-49291 is fixed in 10.65.3. Upgrade to this version or later.
Whether CVE-2026-49291 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade mcp-memory-service to 10.65.3 or later.