← All advisories
CVE-2026-114496mediumUnsafe agent actions2026-11-20

codebase-memory-mcp: a dash-prefixed base_branch made detect_changes write a caller-chosen file via git diff --output, the Windows UI could kill any process, and a .gitignore pattern could stall indexing (CVE-2026-114496, 114497, 114499; fixed 0.10.0)

Three more fixes in codebase-memory-mcp, the MCP server that gives AI coding agents a persistent code graph. Before 0.9.0, the detect_changes tool checked base_branch for shell metacharacters but not for a leading dash, so a value like --output=… was read by git diff as an option and created or overwrote a caller-chosen file with diff output under the server's permissions (CVE-2026-114496; code execution not demonstrated). Before 0.9.1-rc.1 (npm and binaries; 0.10.0 on PyPI), the optional graph UI's POST /api/process-kill skipped the job-ownership check on Windows, letting anyone who can reach the UI terminate any process the server user can (CVE-2026-114497). Before 0.10.0, the .gitignore matcher backtracked without a bound, so one crafted pattern in a repository could stall indexing (CVE-2026-114499).

01.

What it is

CVE-2026-114496 (GHSA-2vj2-hwgx-6f23): an agent following injected instructions can supply base_branch, so treat it as attacker-controlled. Fixed in 0.9.0 (PR #941).

CVE-2026-114497 (GHSA-r2qv-x3rg-p49m): Windows-only; the POSIX path kept the check. Availability impact only. Fixed in 0.9.1-rc.1 (PR #1139).

CVE-2026-114499 (GHSA-cjhf-76h2-4hwg): repeated wildcard groups plus a long path grow matching work exponentially; before worker isolation this stalled the whole server. Fixed in 0.10.0 (PR #1464); the maintainers note the bounded matcher doesn't claim to eliminate every expensive input.

GitHub published the advisories on 17 November 2026; NVD published the CVEs on 20 November 2026.

02.

How to check

  1. npm ls -g codebase-memory-mcp, pip show codebase-memory-mcp, or the binary's version flag.
  2. Check whether the optional graph UI is enabled and reachable from other machines, especially on Windows.
03.

How to fix

  1. Upgrade codebase-memory-mcp to 0.10.0 or later.
  2. Keep the graph UI bound to localhost, and don't index untrusted repositories on old versions.
npm ls -g codebase-memory-mcp; pip show codebase-memory-mcp 2>/dev/null | grep -i '^version'
04.

Sources

Related on VibeVulns
More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.