Information Disclosure in mcp-memory-service (CVE-2026-29787)
Summary
Vulnerability in mcp-memory-service (CVE-2026-29787). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/health/detailed. Mitigation: upgrade to 10.21.0 or later.
Original description
The description as published by the source.
mcp-memory-service is an open-source memory backend for multi-agent systems. Prior to version 10.21.0, the /api/health/detailed endpoint returns detailed system information including OS version, Python version, CPU count, memory totals, disk usage, and the full database filesystem path. When MCP_ALLOW_ANONYMOUS_ACCESS=true is set (required for the HTTP server to function without OAuth/API key), this endpoint is accessible without authentication. Combined with the default 0.0.0.0 binding, this exposes sensitive reconnaissance data to the entire network. This issue has been patched in version 10.21.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-29787 has been found in mcp-memory-service.
Attackers can target a specific entry point like GET /api/health/detailed over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mcp-memory-service to 10.21.0 or later.
If unsure, ask your IT team or search "mcp-memory-service CVE-2026-29787" on the vendor's site.
CVE-2026-29787 (mcp-memory-service) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/health/detailed / require_read_access / get_current_user / platform
Patched: 10.21.0 — 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.
Information disclosure (CWE-200) exists in mcp-memory-service. Attackers reach the vulnerable code path via GET /api/health/detailed without authentication.
Check the vendor advisory for the affected versions of mcp-memory-service. Attack surface: GET /api/health/detailed / require_read_access / get_current_user / platform.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 10.21.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/health/detailed 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 'GET /api/health/detailed' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/health/detailedへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade mcp-memory-service to 10.21.0ステージング環境で 10.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/health/detailed 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 github.com
- patch github.com