● Medium · CVSS 5.3

How to Fix CVE-2026-29787: Information exposure in mcp-memory-service

Q: What is the CVSS score for CVE-2026-29787?

5.3 (Medium). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`.

Q: Where is the official advisory for CVE-2026-29787?

The vendor advisory is at [https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-73hc-m4hx-79pj](https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-73hc-m4hx-79pj). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29787.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-29787 is a information exposure in doobidoo mcp-memory-service. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	5.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	mcp-memory-service < 10.21.0
Fixed in	See vendor advisory
Type (CWE)	CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

What is CVE-2026-29787?

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. The CVSS base score is 5.3 (Medium). The official advisory is at https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-73hc-m4hx-79pj.

Am I affected?

Check the version of mcp-memory-service you are running and compare it against the Affected row above (mcp-memory-service < 10.21.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s mcp-memory-service 2>/dev/null | grep -i ^Version
rpm -q mcp-memory-service 2>/dev/null
command -v mcp-memory-service >/dev/null && mcp-memory-service --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*mcp-memory-service*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "mcp-memory-service" 2>$null

How to fix CVE-2026-29787

Upgrade mcp-memory-service to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade mcp-memory-service
dpkg -s mcp-memory-service | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh mcp-memory-service -y
# or for older releases:
sudo yum update mcp-memory-service -y
rpm -q mcp-memory-service

SUSE / openSUSE


sudo zypper refresh
sudo zypper update mcp-memory-service
rpm -q mcp-memory-service

Node.js / npm


# Update the affected package in your project
npm install mcp-memory-service@latest
npm ls mcp-memory-service
npm audit fix

Python / pip


pip install --upgrade mcp-memory-service
pip show mcp-memory-service | grep -i version

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-29787 affecting mcp-memory-service
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-29787-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*mcp-memory-service*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\mcp-memory-service-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\mcp-memory-service" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "mcp-memory-service" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "mcp-memory-service"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-29787 affecting mcp-memory-service
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-29787-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s mcp-memory-service 2>/dev/null | grep -i ^Version || echo "mcp-memory-service not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q mcp-memory-service || echo "mcp-memory-service not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-29787-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/mcp-memory-service /etc/mcp-memory-service.d /etc/mcp-memory-service.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y mcp-memory-service
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y mcp-memory-service
elif command -v yum >/dev/null; then
    yum update -y mcp-memory-service
elif command -v zypper >/dev/null; then
    zypper --non-interactive update mcp-memory-service
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s mcp-memory-service 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q mcp-memory-service
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-29787" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-29787"

Disable the affected service (Linux)


sudo systemctl stop mcp-memory-service 2>/dev/null || true
sudo systemctl disable mcp-memory-service 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s mcp-memory-service 2>/dev/null | grep -i ^Version
rpm -q mcp-memory-service 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*mcp-memory-service*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-28051: Improper control of filename for include/require statement in php program ('php. — Improper control of filename for include/require statement in php program ('php.
How to Fix CVE-2026-41571: Improper Authentication in note-mark — Improper Authentication in note-mark
How to Fix CVE-2026-39383: Server-Side Request Forgery (SSRF) in gotenberg , Server-Side Request Forgery (SSRF) in gotenberg
How to Fix CVE-2026-34951: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') , CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
How to Fix CVE-2026-8813: Access Control Bypass in exifreader , Access Control Bypass in exifreader

Is CVE-2026-29787 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-29787?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-29787?

5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.

Where is the official advisory for CVE-2026-29787?

The vendor advisory is at https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-73hc-m4hx-79pj. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29787.

References

Official vendor advisory: https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-73hc-m4hx-79pj
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29787
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/doobidoo/mcp-memory-service/commit/18f4323ca92763196aa2922f691dfbeb6bd84e48

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*