Summary
@cyanheads/git-mcp-server vulnerable to command injection in several tools
Impact
Command Injection / Remote Code Execution (RCE)
Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.
CVE-2025-53107 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.5); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
To mitigate this vulnerability, I suggest to avoid using child_process.exec with untrusted input. Instead, use a safer API such as child_process.execFile, which allows you to pass arguments as a separate array, avoiding shell interpretation entirely.
Frequently Asked Questions
- What is CVE-2025-53107? CVE-2025-53107 is a high-severity command injection vulnerability in @cyanheads/git-mcp-server (npm), affecting versions <= 2.1.4. It is fixed in 2.1.5. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
- How severe is CVE-2025-53107? CVE-2025-53107 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @cyanheads/git-mcp-server are affected by CVE-2025-53107? @cyanheads/git-mcp-server (npm) versions <= 2.1.4 is affected.
- Is there a fix for CVE-2025-53107? Yes. CVE-2025-53107 is fixed in 2.1.5. Upgrade to this version or later.
- Is CVE-2025-53107 exploitable, and should I be worried? Whether CVE-2025-53107 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-53107 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-53107? Upgrade
@cyanheads/git-mcp-serverto 2.1.5 or later.