CVE-2026-54561 MCP Memory Keeper: Arbitrary local file read in mcp-memory-keeper context_import via unvalidated filePath
An attacker can read arbitrary local files via path traversal in the context_import tool, exposing sensitive data like credentials and keys.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54561?
CVE-2026-54561 is a medium-severity path traversal vulnerability in mkreyman mcp-memory-keeper, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
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.
Which versions are affected by CVE-2026-54561?
2 open source packages ship an affected version, including mcp-memory-keeper.
| Package | Affected | Fixed in |
|---|---|---|
mcp-memory-keeper npm | All versions | 0.13.0 |
mcp-memory-keeper npm | All versions | 0.13.0 |
How do I fix CVE-2026-54561?
Upgrade mcp-memory-keeper to 0.13.0 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-54561 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54561 exists.
Sources
Also known as GHSA-f7wf-v2vw-mpcx.