AI Stack Alert Medium CVE-2026-114496 For AppSec, AI Eng, SOC / IR AI-assisted
codebase-memory-mcp before 0.9.0: detect_changes base_branch argument enables arbitrary file write via git option injection
codebase-memory-mcp provides local code intelligence through MCP tools. Before version 0.9.0, the detect_changes tool checked base_branch for shell metacharacters but did not check for a leading dash before passing it to git diff. An option-shaped value such as --output could therefore be read by Git as an option, letting a caller create or overwrite a chosen file with diff output under the server's permissions.
Why it matters
Any caller able to invoke the MCP tool can write files as the server process user, which may affect local developer machines or agent hosts. The source states that arbitrary code execution was not demonstrated.
Do this
- Upgrade codebase-memory-mcp to version 0.9.0 or later.
- Inventory MCP server deployments that include codebase-memory-mcp and confirm their installed version.
- Restrict which agents or users can call the detect_changes tool until patched.
- Run the MCP server under a low-privilege account with write access limited to required project directories.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 5.5CVSS
- NoPublic PoC
- 27/100Priority
- 80%Confidence
Evidence
“Prior to 0.9.0, the detect_changes tool validated the base_branch argument for shell metacharacters but omitted the leading-dash check”
“allowing a caller to create or overwrite a caller-chosen file with Git diff output under the server process's permissions.”
“Arbitrary code execution was not demonstrated. This issue is fixed in version 0.9.0.”
Sources
Affected / related
codebase-memory-mcp, git
Published 2026-11-20 20:17 UTC · updated 2026-11-20 22:35 UTC · AI-assisted summary, checked against quoted sources · How we score