Summary
mcp-memory-service Vulnerable to System Information Disclosure via Health Endpoint
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.
Details
Vulnerable Code
health.py:90-101 - System information collection
system_info = {
"platform": platform.system(), # e.g., "Linux", "Darwin"
"platform_version": platform.version(), # Full OS kernel version string
"python_version": platform.python_version(),# e.g., "3.12.1"
"cpu_count": psutil.cpu_count(), # CPU core count
"memory_total_gb": round(memory_info.total / (1024**3), 2),
"memory_available_gb": round(memory_info.available / (1024**3), 2),
"memory_percent": memory_info.percent,
"disk_total_gb": round(disk_info.total / (1024**3), 2),
"disk_free_gb": round(disk_info.free / (1024**3), 2),
"disk_percent": round((disk_info.used / disk_info.total) * 100, 2)
}
health.py:131-132 - Database path disclosure
if hasattr(storage, 'db_path'):
storage_info["database_path"] = storage.db_path # Full filesystem path
Authentication Bypass Path
The /api/health/detailed endpoint uses require_read_access which calls get_current_user. When MCP_ALLOW_ANONYMOUS_ACCESS=true, the auth middleware grants access:
# middleware.py:372-379
if ALLOW_ANONYMOUS_ACCESS:
logger.debug("Anonymous access explicitly enabled, granting read-only access")
return AuthenticationResult(
authenticated=True,
client_id="anonymous",
scope="read",
auth_method="none"
)
Note: The basic /health endpoint (line 68) has no auth dependency at all and returns version and uptime information unconditionally.
Information Exposed
| Field | Example Value | Reconnaissance Value |
|---|---|---|
platform |
"Linux" |
OS fingerprinting |
platform_version |
"#1 SMP PREEMPT_DYNAMIC..." |
Kernel version → CVE targeting |
python_version |
"3.12.1" |
Python CVE targeting |
cpu_count |
8 |
Resource enumeration |
memory_total_gb |
32.0 |
Infrastructure profiling |
database_path |
"/home/user/.mcp-memory/memories.db" |
Username + file path disclosure |
database_size_mb |
45.2 |
Data volume estimation |
Attack Scenario
- Attacker scans the local network for services on port 8000
- Finds mcp-memory-service with HTTP enabled and anonymous access
- Calls
GET /api/health/detailed(no credentials needed) - Receives OS version, Python version, full database path (revealing username), system resources
- Uses this information to:
- Target known CVEs for the specific OS/Python version
- Identify the database file location for potential direct access
- Profile the system for further attacks
PoC
# Show the system info that would be exposed
import platform, psutil
system_info = {
"platform": platform.system(),
"platform_version": platform.version(),
"python_version": platform.python_version(),
"cpu_count": psutil.cpu_count(),
"memory_total_gb": round(psutil.virtual_memory().total / (1024**3), 2),
}
print(system_info) # All of this is returned to unauthenticated users
Impact
- 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
CVE-2026-29787 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (10.21.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-29787? CVE-2026-29787 is a medium-severity security vulnerability in mcp-memory-service (pip), affecting versions < 10.21.0. It is fixed in 10.21.0.
- How severe is CVE-2026-29787? CVE-2026-29787 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of mcp-memory-service are affected by CVE-2026-29787? mcp-memory-service (pip) versions < 10.21.0 is affected.
- Is there a fix for CVE-2026-29787? Yes. CVE-2026-29787 is fixed in 10.21.0. Upgrade to this version or later.
- Is CVE-2026-29787 exploitable, and should I be worried? Whether CVE-2026-29787 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-29787 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-29787? Upgrade
mcp-memory-serviceto 10.21.0 or later.