Skip to content
Fencer Intel
medium 5.5

CVE-2026-114496 json

codebase-memory-mcp: git option injection through base_branch in detect_changes allows writing a file outside the project

published 3d ago modified 15h ago also GHSA-2vj2-hwgx-6f23 , EUVD-2026-131799

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository DeusData/codebase-memory-mcp. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

Is CVE-2026-114496 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm codebase-memory-mcp
<0.9.0
0.9.0

Affected products

  • DeusData codebase-memory-mcp

Classification

Weakness
  • CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of DeusData/codebase-memory-mcp published their own advisory on GitHub. Reviewed sources take precedence over it.