← Back
CVE-2026-54561
Path Traversal in mcp-memory-keeper (CVE-2026-54561)
Summary
path traversal in mcp-memory-keeper (CVE-2026-54561). Risk of unauthorized operations or information disclosure. Exploitable via ``context_import``. Mitigation: upgrade to `0.13.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54561** has been found in mcp-memory-keeper.
Attackers can target a specific entry point like ``context_import`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade mcp-memory-keeper to **0.13.0** or later.
If unsure, ask your IT team or search "mcp-memory-keeper CVE-2026-54561" on the vendor's site.
CVE-2026-54561 (mcp-memory-keeper) — CWE-22 /
Attack surface: `context_import` / `filePath` / `fs.readFileSync` / `context_get`
Patched: `0.13.0` — apply immediately
Workaround: Upgrade to **`>= 0.13.0`**.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in mcp-memory-keeper. Attackers reach the vulnerable code path via ``context_import`` without authentication.
📍 Affected scope
mcp-memory-keeper — . Attack surface: `context_import` / `filePath` / `fs.readFileSync` / `context_get`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.13.0**.
🛡️ Workaround
Workaround: Upgrade to **`>= 0.13.0`**.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'mcp-memory-keeper' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-memory-keeper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mcp-memory-keeper` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to **`>= 0.13.0`**.パッチが適用されるまでの応急処置として、Upgrade to **`>= 0.13.0`**. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade mcp-memory-keeper to 0.13.0ステージング環境で 0.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
mcp-memory-keeper
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.13.0"}]}]
References
- web https://github.com/mkreyman/mcp-memory-keeper/security/advisories/GHSA-f7wf-v2vw-mpcx
- web https://github.com/mkreyman/mcp-memory-keeper/issues/35
- web https://github.com/mkreyman/mcp-memory-keeper/pull/36
- web https://github.com/mkreyman/mcp-memory-keeper/commit/84f6dfa692736a34ff36e2d2cf2188b71facf73b
- web https://github.com/mkreyman/mcp-memory-keeper/releases/tag/v0.13.0
- web https://github.com/advisories/GHSA-f7wf-v2vw-mpcx