Vulnerability in mcp-memory-service (CVE-2026-50027)
Summary
Vulnerability in mcp-memory-service (CVE-2026-50027). Successful exploitation can lead to full system takeover. Exploitable via POST /upload. Mitigation: upgrade to 10.67.1 or later.
Original description
The description as published by the source.
Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete
Summary
All HTTP routes under /api/documents/* in mcp-memory-service are served without any authentication dependency, even when the server is configured with an API key (MCP_API_KEY) or OAuth. An unauthenticated remote attacker can upload arbitrary content into the memory store (write), retrieve stored document content (read), and permanently delete memories belonging to authenticated users (delete) — all without supplying any credentials. The /api/memories counterpart correctly enforces authentication, making this an inconsistent and exploitable authentication boundary. CVSS 9.8 Critical.
Details
The documents.py router is instantiated without any router-level dependencies= parameter and the file does not import Depends at all, so no authentication guard is present on any of its routes:
src/mcp_memory_service/web/api/documents.py:33—from fastapi import APIRouter, UploadFile, File, Form, HTTPException, BackgroundTasks(Dependsis absent)src/mcp_memory_service/web/api/documents.py:43—router = APIRouter()(nodependencies=argument)
The affected endpoints and their data-flow sinks are:
| Route | Line (source) | Sink | Line (sink) |
|---|---|---|---|
POST /upload |
149 | storage.store(memory) |
449 |
POST /batch-upload |
— | storage.store(memory) |
— |
GET /history |
— | upload metadata response | — |
| `GE… |
Source: GitHub Security Advisories (Global) 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-50027 has been found in mcp-memory-service.
Attackers can target a specific entry point like POST /upload over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade mcp-memory-service to 10.67.1 or later.
If unsure, ask your IT team or search "mcp-memory-service CVE-2026-50027" on the vendor's site.
CVE-2026-50027 (mcp-memory-service) — CWE-306 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /upload / POST /batch-upload / GET /history / GET /search-content/{upload_id}
Patched: 10.67.1 — 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-306) exists in mcp-memory-service. Attackers reach the vulnerable code path via POST /upload without authentication.
Check the vendor advisory for the affected versions of mcp-memory-service. Attack surface: POST /upload / POST /batch-upload / GET /history / GET /search-content/{upload_id}.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 10.67.1.
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 /upload 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 /upload' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /uploadへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade mcp-memory-service to 10.67.1ステージング環境で 10.67.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /upload on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com