mcp-memory-keeper: Arbitrary local file read in context_import via unvalidated filePath

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-54561: 0.25% estimated exploitation activity in the next 30 days; percentile 16.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact contextimport passed the caller-supplied filePath directly to fs.readFileSync with no path confinement. A malicious MCP client — or an LLM agent that is prompt-injected into calling the tool — could point filePath at any file readable by the server process, outside any session or export directory: - Full disclosure (JSON files): a valid-JSON target (e.g. another user's exported session, or a .json credential / service-account file) is parsed and imported into the caller's session, then retrievable verbatim via contextget / contextexport. - Partial disclosure (any file): for a non-JSON target (e.g. /etc/passwd, an SSH key, a .env), JSON.parse throws and V8 includes a snippet of the file's leading bytes in the SyntaxError message, which was returned verbatim to the caller. Both ../ traversal and absolute paths worked — there was no path confinement of any kind. In a typical MCP deployment the server runs on the developer's machine, so the reachable set includes other users'…

Published by the source

17 Jul 2026, 19:23 UTC

Last modified by the source

31 Jul 2026, 05:15 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f7wf-v2vw-mpcx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f7wf-v2vw-mpcx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54561

Advisory: mcp-memory-keeper: Arbitrary local file read in context_import via unvalidated filePath
IDs: CVE-2026-54561, GHSA-f7wf-v2vw-mpcx
Record: https://patchnext.com/advisories/cve-2026-54561 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mcp-memory-keeper 0.13.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mcp-memory-keeper: affected < 0.13.0; fixed in 0.13.0

## Suggested inspection (read-only)
- `npm ls mcp-memory-keeper --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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-keeper.
- 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://osv.dev/vulnerability/GHSA-f7wf-v2vw-mpcx (OSV record GHSA-f7wf-v2vw-mpcx lists affected ranges: npm mcp-memory-keeper >=0 <0.13.0 (fixed))
- Verified: https://github.com/advisories/GHSA-f7wf-v2vw-mpcx (GitHub-reviewed advisory GHSA-f7wf-v2vw-mpcx lists affected ranges: npm mcp-memory-keeper >=0 <0.13.0)

Commands are suggestions: review each one before running it.