Skip to content
Fencer Vulns
high 7.5

CVE-2025-53107 in the critical feed json

@cyanheads/git-mcp-server vulnerable to command injection in several tools

published 2025-06-30 16 mo ago modified 2026-06-17 4 mo ago also GHSA-3q26-f695-pp76 , EUVD-2025-19657

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
24.5%
EPSS 24.5% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

@cyanheads/git-mcp-server is an MCP server designed to interact with Git repositories. Prior to version 2.1.5, there is a command injection vulnerability caused by the unsanitized use of input parameters within a call to child_process.exec, enabling an attacker to inject arbitrary system commands. Successful exploitation can lead to remote code execution under the server process's privileges. The server constructs and executes shell commands using unvalidated user input directly within command-line strings. This introduces the possibility of shell metacharacter injection (|, >, &&, etc.). An MCP Client can be instructed to execute additional actions for example via indirect prompt injection when asked to read git logs. This issue has been patched in version 2.1.5.

Patch / fix

  • npm @cyanheads/git-mcp-server 2.1.5

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
16 mo ago

Exploit prediction

24.54% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm @cyanheads/git-mcp-server
<2.1.5
2.1.5

Affected products

  • cyanheads git-mcp-server

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Vulns 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.