codebase-memory-mcp file write in git diff via base_branch
- Exploited
- No known exploitation
- Fix
- Fixed in 0.9.0
- Who is exposed
- Not reported
Summary
The codebase-memory-mcp tool from DeusData mishandles a branch name in its detect_changes tool, so git reads a dash-prefixed value as a command option instead of a branch name. A local user with low privileges, and no user action needed, can use this to create or overwrite a file of their choice with git diff output, with the server process's permissions.
Written by a model
Original description
codebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.0, the detect_changes tool validated the base_branch argument for shell metacharacters but omitted the leading-dash check before placing the value in the revision position of a git diff command. Git therefore interpreted an option-shaped base_branch value, including --output, as a command option instead of a revision, 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.
What to do
Upgrade to a fixed version: 0.9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-114496 (codebase-memory-mcp: git option injection through base_branch in detect_changes allows writing a file outside the project), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-114496 (entry last updated 2026-11-20):
Affected:
- DeusData codebase-memory-mcp: fixed in 0.9.0
Fixed versions: 0.9.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-114496 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114496 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DeusData/codebase-memory-mcp/security/advisories/GHSA-2vj2-hwgx-6f23
- https://github.com/DeusData/codebase-memory-mcp/pull/941
- https://github.com/DeusData/codebase-memory-mcp/commit/72e6a14adb50a37a245eb6ec79c9eb31eee48951
- https://github.com/DeusData/codebase-memory-mcp/releases/tag/v0.9.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-114496
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114496"}.Affected versions
- DeusData codebase-memory-mcpfixed in 0.9.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.5/10CVSS 5.5
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · DeusData/codebase-memory-mcp · Advisory GHSA-2vj2-hwgx-6f23 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-114496 |
| Record | NVD · CVE-2026-114496 |
| Other links 3 | |
| Repository | GitHub · DeusData/codebase-memory-mcp · Pull request #941 |
| Repository | GitHub · DeusData/codebase-memory-mcp · Commit 72e6a14a |
| Repository | GitHub · DeusData/codebase-memory-mcp · Release v0.9.0 |
Questions about CVE-2026-114496
Is CVE-2026-114496 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-114496?
codebase-memory-mcp: before 0.9.0.
Source: cve.now feed data
How do I fix CVE-2026-114496?
Upgrade to a fixed version: 0.9.0.
Source: cve.now feed data
Related
- CVE-2026-114495codebase-memory-mcp: Heap buffer overflow on artifact import via int-truncated decompression capacity
- CVE-2026-114494codebase-memory-mcp: Stack out-of-bounds write in query_graph via a RETURN or WITH clause with more than 32 items
- CVE-2026-114499codebase-memory-mcp: Catastrophic backtracking in .gitignore glob matching lets a repository stall the indexer
- CVE-2026-114497codebase-memory-mcp: UI process-kill route skipped the ownership check on Windows, allowing termination of arbitrary processes
- CVE-2026-132234In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings
- CVE-2026-132232In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings
No corrections so far. Something wrong on this page? Report an error.