mcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete
CVE-2026-50027GHSA-84hp-mqvj-3p8h
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mcp-memory-service 10.67.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI mcp-memory-service
- Affected
- < 10.67.1
- Fixed in
- 10.67.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-84hp-mqvj-3p8h lists affected ranges: PyPI mcp-memory-service >=0 <10.67.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-84hp-mqvj-3p8h lists affected ranges: PyPI mcp-memory-service >=0 <10.67.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-50027: 0.96% estimated exploitation activity in the next 30 days; percentile 61.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete Summary All HTTP routes under /api/documents/ in mcp-memory-service are served without any authentication dependency, even when the server is configured with an API key (MCPAPIKEY) or OAuth. An unauthenticated remote attacker can upload arbitrary content into the memory store (write), retrieve stored document content (read), and permanently delete memories belonging to authenticated users (delete) — all without supplying any credentials. The /api/memories counterpart correctly enforces authentication, making this an inconsistent and exploitable authentication boundary. CVSS 9.8 Critical. Details The documents.py router is instantiated without any router-level dependencies= parameter and the file does not import Depends at all, so no authentication guard is present on any of its routes: - src/mcpmemoryservice/web/api/documents.py:33 — from fastapi import APIRouter, UploadFile, File, Form,…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-84hp-mqvj-3p8h
- Revision 2 · amended ·
Amended from osv record GHSA-84hp-mqvj-3p8h
- Revision 1 · created ·
Published from ghsa record GHSA-84hp-mqvj-3p8h
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-50027 Advisory: mcp-memory-service: Missing Authentication on Document API Endpoints Allows Unauthenticated Memory Read/Write/Delete IDs: CVE-2026-50027, GHSA-84hp-mqvj-3p8h Record: https://patchnext.com/advisories/cve-2026-50027 (revision 3, source checked 26 Oct 2026, 13:46 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) 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.67.1. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI mcp-memory-service: affected < 10.67.1; fixed in 10.67.1 ## 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://github.com/advisories/GHSA-84hp-mqvj-3p8h (GitHub-reviewed advisory GHSA-84hp-mqvj-3p8h lists affected ranges: PyPI mcp-memory-service >=0 <10.67.1) - Verified: https://osv.dev/vulnerability/GHSA-84hp-mqvj-3p8h (OSV record GHSA-84hp-mqvj-3p8h lists affected ranges: PyPI mcp-memory-service >=0 <10.67.1 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…