mcp-memory-service Vulnerable to System Information Disclosure via Health Endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-29787: 0.41% estimated exploitation activity in the next 30 days; percentile 35.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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 MCPALLOWANONYMOUSACCESS=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 health.py:131-132 - Database path disclosure Authentication Bypass Path The /api/health/detailed endpoint uses requirereadaccess which calls getcurrentuser. When MCPALLOWANONYMOUSACCESS=true, the auth middleware grants access: 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 |…

Published by the source

5 Mar 2026, 21:42 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-73hc-m4hx-79pj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-73hc-m4hx-79pj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-29787

Advisory: mcp-memory-service Vulnerable to System Information Disclosure via Health Endpoint
IDs: CVE-2026-29787, GHSA-73hc-m4hx-79pj
Record: https://patchnext.com/advisories/cve-2026-29787 (revision 2, source checked 26 Oct 2026, 13:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mcp-memory-service 10.21.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mcp-memory-service: affected < 10.21.0; fixed in 10.21.0

## Suggested inspection (read-only)
- `python -m pip show mcp-memory-service`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mcp-memory-service.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-73hc-m4hx-79pj (OSV record GHSA-73hc-m4hx-79pj lists affected ranges: PyPI mcp-memory-service >=0 <10.21.0 (fixed))
- Verified: https://github.com/advisories/GHSA-73hc-m4hx-79pj (GitHub-reviewed advisory GHSA-73hc-m4hx-79pj lists affected ranges: PyPI mcp-memory-service >=0 <10.21.0)

Commands are suggestions: review each one before running it.