Skip to main content
VulnerabilityPublished Updated

CVE-2026-49291: doobidoo mcp-memory-service · Missing Authorization

Affects doobidoo mcp-memory-serviceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 10.65.3 soon.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.65.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade doobidoo mcp-memory-service to 10.65.3.

Affected software

ProductAffectedFixed in
doobidoomcp-memory-serviceAffected
  • <10.65.3
Fixed in
  • 10.65.3
PyPImcp-memory-servicepkg:pypi/mcp-memory-serviceOther threatsAffected
  • <10.65.3
Fixed in
  • 10.65.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to version 10.65.3 or later, where the authorization checks are corrected to require write scope for mutating operations. No other mitigation is indicated. Patch status is not explicitly confirmed but the description states version 10.65.3 patches the issue.

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.

References

Community reviews

Loading reviews…