mcp-memory-service Vulnerable to System Information Disclosure via Health Endpoint
CVE-2026-29787 · GHSA-73hc-m4hx-79pj · published 2026-03-05 · updated 2026-03-09
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.41%
- Fixed in
- 10.21.0
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
OS fingerprinting: Exact OS and kernel version enables targeted exploit selection Path disclosure: Database path reveals username, home directory structure, and file locations Resource enumeration: CPU, memory, and disk info reveal infrastructure scale Reconnaissance enablement: Combined information significantly reduces attacker effort for follow-up attacks
Upgrade mcp-memory-service to 10.21.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
1. Remove system details from default health endpoint - return only status, version, uptime: 2. Do not expose databasepath** - this leaks the filesystem structure:
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-memory-service | PyPI | < 10.21.0 | 10.21.0 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- Criticalmcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Deletemcp-memory-service
- Highmcp-memory-service: OAuth read-only clients can write and delete memories through MCP tools/callmcp-memory-service
- Highmcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theftmcp-memory-service
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.