CVE-2026-49291: doobidoo mcp-memory-service authorization bypass in JSON-RPC endpoint

CVE-2026-49291 · Severity: high · CVSS 8.1 · Published 2026-06-19

A vulnerability in the mcp-memory-service allows users with restricted "read-only" access to bypass security controls and perform unauthorized actions. Specifically, an attacker can use the Model Context Protocol (MCP) interface to create or delete stored memories, even if their account is explicitly forbidden from doing so via standard interfaces. This could lead to the corruption of the memory database, loss of user data, and unauthorized modification of the information used by AI agents.

Technologies: mcp-memory-service (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-49291 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49291 being exploited in the wild.
How severe is CVE-2026-49291?
High severity, with a CVSS score of 8.1, published 19 June 2026.
Which products and versions are affected?
Doobidoo Mcp-Memory-Service < 10.65.3, <= 10.65.1; mcp-memory-service (PyPI) ECOSYSTEM:introduced=0,fixed=10.65.3.
Is there a fix for CVE-2026-49291?
Yes. mcp-memory-service (PyPI): upgrade to 10.65.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49291 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-49291?
Check whether you run Doobidoo Mcp-Memory-Service or mcp-memory-service (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • mcp-memory-service (PyPI): upgrade to 10.65.3 or later
    pip install "mcp-memory-service>=10.65.3"

Technical details

The vulnerability is a missing authorization check (CWE-862) in the `mcp_endpoint` located in `src/mcp_memory_service/web/api/mcp.py`. While the REST API correctly enforces `require_write_access` for mutating operations, the MCP JSON-RPC endpoint only requires `require_read_access` for the entire `/mcp` route. When processing `tools/call` requests, the service dispatches calls to tools like `store_memory` and `delete_memory` without verifying if the authenticated user possesses the necessary write permissions. An attacker with a valid read-only OAuth token can send a crafted JSON-RPC request to the `/mcp` endpoint to modify or destroy data. The issue is patched in version 10.65.3.

Affected products

  • doobidoo mcp-memory-service <= 10.65.1

Identifiers

  • CVE-2026-49291
  • GHSA-2r68-g678-7qr3
  • PYSEC-2026-2622

Timeline

  • 2026-05-25: disclosed: Advisory published by doobidoo
  • 2026-06-19: advisory: NVD publication date
  • 2026-06-26: advisory: GitHub Advisory Database publication date
  • 2026-06-26: patched: Version 10.65.3 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.