Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

mcp-memory-keeper

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.2npmAmendedPublished

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

    CVE-2026-54561 · GHSA-f7wf-v2vw-mpcx

    Affected
    • npm mcp-memory-keeper < 0.13.0
    Fixed in
    0.13.0· Vendor fix available
    Issue
    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'…

    Recommended action: Upgrade to 0.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →