Vulnerability · Published Sep 15, 2026 · Assigned by GitHub_M

CVE-2026-54561MCP Memory Keeper: Arbitrary local file read in mcp-memory-keeper context_import via unvalidated filePath

Medium 6.2

In plain English

A medium-severity path traversal in mcp-memory-keeper from mkreyman. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 16% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)6.2Medium
Exploit odds (30 days)0.2%top 83.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

MCP Memory Keeper is an MCP server for persistent context management in AI coding assistants. Prior to 0.13.0, context_import in src/index.ts passes the caller-controlled filePath directly to fs.readFileSync without restricting the path to an export directory. An MCP client, including an LLM agent induced to call the tool, can use ../ traversal or an absolute path to target any file readable by the server process. A valid JSON file is parsed and imported into the caller's session, allowing its full contents to be retrieved through context_get or context_export, while JSON.parse errors for non-JSON files can return leading file bytes in a SyntaxError message. The two disclosure modes can expose other exported sessions, JSON credentials or service-account files, environment files, and portions of SSH keys or other local files. This issue is fixed in version 0.13.0.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmmcp-memory-keeper0.13.0GHSA-f7wf-v2vw-mpcx

Affected products (as reported)

VendorProductVersions
mkreyman mcp-memory-keeper < 0.13.0

Weakness: CWE-22, CWE-209 · Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References