Skip to main content
Public proof of conceptFix available

CVE-2025-53107

A public proof of concept exists; no exploitation attested.

  • Published2025-07-01
  • Fixed in2.1.5
  • WeaknessCWE-77

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

@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.

Timeline

dates in UTC
  1. 2025-07-0118:15CVE publishedNVD

Versions per branch

OSV
@cyanheads/git-mcp-server
BranchAffectedFixed in
2.1< 2.1.52.1.5

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • cyanheads git-mcp-server
    Affected
    • = < 2.1.5no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-07-01

Fix

  1. Update @cyanheads/git-mcp-server to 2.1.5

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2025-07-01
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-77known since 2026-10-23
  • FIRST EPSSEPSS score24.5 %read 2026-11-09
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2025-06-30

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2025-07-01
Last Modified
2026-06-17
NVD status
Deferred
GitHub Advisory
GHSA-3q26-f695-pp76

Frequently asked questions

What is CVE-2025-53107?

@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.

Is CVE-2025-53107 actively exploited?

A proof-of-concept exploit exists for CVE-2025-53107, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2025-53107?

CVE-2025-53107 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running @cyanheads/git-mcp-server? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record