Vulnerability in mcp-memory-service (CVE-2026-49291)
Summary
Vulnerability in mcp-memory-service (CVE-2026-49291). Data can be tampered with by attackers. Exploitable via POST /api/memories. Mitigation: upgrade to 10.65.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49291 has been found in mcp-memory-service.
Attackers can target a specific entry point like POST /api/memories over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade mcp-memory-service to 10.65.3 or later.
If unsure, ask your IT team or search "mcp-memory-service CVE-2026-49291" on the vendor's site.
CVE-2026-49291 (mcp-memory-service) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/memories / POST /mcp / read / store_memory
Patched: 10.65.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in mcp-memory-service. Attackers reach the vulnerable code path via POST /api/memories.
Check the vendor advisory for the affected versions of mcp-memory-service. Attack surface: POST /api/memories / POST /mcp / read / store_memory.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 10.65.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/memories requests with malformed payloads or SQL meta-characters. Run grep -r 'mcp-memory-service' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-memory-service' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mcp-memory-serviceを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/memories' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/memoriesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade mcp-memory-service to 10.65.3ステージング環境で 10.65.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/memories on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package pypi.org
- package github.com
- web web.archive.org
- web web.archive.org
- web github.com