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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2025-53107: 24.54% estimated exploitation activity in the next 30 days; percentile 97.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A command injection vulnerability exists in the git-mcp-server MCP Server. The vulnerability is caused by the unsanitized use of input parameters within a call to childprocess.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.). Details The MCP Server exposes tools (gitadd, gitinit, gitlogs, etcc) to perform several git operations. An MCP Client can be instructed to execute additional actions for example via indirect prompt injection when asked to read git logs. Below some example of vulnerable code and different ways to test this vulnerability including a real example of indirect prompt injection that can lead to arbitrary command injection. Vulnerable code The following…

Published by the source

30 Jun 2025, 18:50 UTC

Last modified by the source

4 Feb 2026, 02:22 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3q26-f695-pp76

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3q26-f695-pp76

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53107

Advisory: @cyanheads/git-mcp-server vulnerable to command injection in several tools
IDs: CVE-2025-53107, GHSA-3q26-f695-pp76
Record: https://patchnext.com/advisories/cve-2025-53107 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @cyanheads/git-mcp-server 2.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @cyanheads/git-mcp-server: affected <= 2.1.4; fixed in 2.1.5

## Suggested inspection (read-only)
- `npm ls @cyanheads/git-mcp-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @cyanheads/git-mcp-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3q26-f695-pp76 (OSV record GHSA-3q26-f695-pp76 lists affected ranges: npm @cyanheads/git-mcp-server >=0 <2.1.5 (fixed))
- Verified: https://github.com/advisories/GHSA-3q26-f695-pp76 (GitHub-reviewed advisory GHSA-3q26-f695-pp76 lists affected ranges: npm @cyanheads/git-mcp-server >=0 <=2.1.4)

Commands are suggestions: review each one before running it.