# CVE-2026-29787: mcp-memory-service: System Information Disclosure via Health Endpoint

> Unauthenticated attackers can access detailed system information via the health endpoint when anonymous access is enabled, exposing sensitive reconnaissance data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-73hc-m4hx-79pj, PYSEC-2026-2623

## What is CVE-2026-29787?

CVE-2026-29787 is a medium-severity vulnerability in doobidoo mcp-memory-service, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-29787?

3 open source packages ship an affected version, including mcp-memory-service. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mcp-memory-service` | PyPI | All versions | 10.21.0 |
| `mcp-memory-service` | PyPI | All versions | 10.21.0 |
| `mcp-memory-service` | PyPI | All versions | 10.21.0 |

Products: Doobidoo Mcp-Memory-Service.

## How do I fix CVE-2026-29787?

Upgrade mcp-memory-service to 10.21.0 or later.

## Is CVE-2026-29787 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29787 exists.

## Other vulnerabilities in doobidoo mcp-memory-service

- [CVE-2026-33010](https://insights.sbomify.com/CVE-2026-33010/): mcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theft (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29787 and fix it if it is affected.

What it is: CVE-2026-29787 is a medium-severity vulnerability in doobidoo mcp-memory-service, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29787 exists.

Affected packages and fixed versions:
- mcp-memory-service (PyPI): affected all versions; fixed in 10.21.0
- mcp-memory-service (PyPI): affected all versions; fixed in 10.21.0
- mcp-memory-service (PyPI): affected all versions; fixed in 10.21.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29787/ (Markdown: https://insights.sbomify.com/CVE-2026-29787/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29787
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29787
- OSV: https://osv.dev/vulnerability/CVE-2026-29787

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29787/
Summaries are generated and may contain mistakes; the official description above is the record.