CVE-2026-54561

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.2
EG Score
6.2(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity62% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 17, 2026

Last Modified

September 15, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github, github_pr.
github_commit

commit e0ab521a9e83 (mkreyman/mcp-memory-keeper)

Fix landed in mkreyman/mcp-memory-keeper commit e0ab521a9e83 — awaiting tagged release

https://github.com/mkreyman/mcp-memory-keeper/commit/e0ab521a9e8343bcab1ca60ccc3601e4d86eaa97
github_commit

commit b93695684680 (mkreyman/mcp-memory-keeper)

Fix landed in mkreyman/mcp-memory-keeper commit b93695684680 — awaiting tagged release

https://github.com/mkreyman/mcp-memory-keeper/commit/b9369568468007c85f8aec3ae09ca6f611285bc5
github_commit

commit 58640c22e037 (mkreyman/mcp-memory-keeper)

Fix landed in mkreyman/mcp-memory-keeper commit 58640c22e037 — awaiting tagged release

https://github.com/mkreyman/mcp-memory-keeper/commit/58640c22e037572e0b03bc0aa25d015ea98dcc6d
github_pr

fix(security): confine context_import to exports dir (#35)

Fix merged in mkreyman/mcp-memory-keeper PR #36 on 2026-06-05 — awaiting tagged release

https://github.com/mkreyman/mcp-memory-keeper/pull/36
generic🟡 PoC Available

[Potential Vulnerability] Arbitrary Local File Read via Unvalidated context_import.filePath · Issue #35 · mkreyman/mcp-memory-keeper · GitHub

https://github.com/mkreyman/mcp-memory-keeper/issues/35
github Patch Available

Arbitrary local file read in mcp-memory-keeper context_import via unvalidated filePath · Advisory · mkreyman/mcp-memory-keeper · GitHub

https://github.com/mkreyman/mcp-memory-keeper/security/advisories/GHSA-f7wf-v2vw-mpcx

Vendor Advisories for CVE-2026-54561(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
mcp-memory-keeper—0.13.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-17 10:14 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-15 18:36 UTCEG score recompute
  6. 2026-09-15 17:34 UTCEG score recompute
  7. 2026-07-30 18:59 UTCEG score recompute
  8. 2026-07-26 11:17 UTCEG score recompute
  9. 2026-07-23 03:19 UTCEG score recompute
  10. 2026-07-17 20:00 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54561?
CVE-2026-54561 is a medium vulnerability published on July 17, 2026. MCP Memory Keeper is an MCP server for persistent context management in AI coding assistants. Prior to 0.13.0, contextimport 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…
When was CVE-2026-54561 disclosed?
CVE-2026-54561 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54561 actively exploited?
CVE-2026-54561 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.4% of all scored CVEs.
What is the CVSS score of CVE-2026-54561?
CVE-2026-54561 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-54561?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54561, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54561

Explore →

Is Your Infrastructure Affected by CVE-2026-54561?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs