CVE-2026-85626
Received Received - Intake

Argument Injection in git-mcp-server via Git Command Options

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: VulnCheck

Description
git-mcp-server 2.15.1 contains an argument injection vulnerability in the ref and object parameters of git_log, git_diff, and git_show tools that lack leading-dash validation. Attackers can inject git command-line options like --output= to write files outside the repository to arbitrary paths accessible by the process.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-04
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
CVE-2026-85626
EUVD
EUVD-2026-71233

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
cyanheads git-mcp-server to 2.15.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-88 The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an argument injection flaw in git-mcp-server version 2.15.1. It affects the ref and object parameters of tools like git_log, git_diff, and git_show. These parameters are passed as plain strings without validation for leading dashes, allowing attackers to inject Git command-line options such as --output= to write files outside the repository to arbitrary paths accessible by the process.

Detection Guidance

Check for unusual file writes in system directories by monitoring git-mcp-server processes. Look for commands containing --output= or similar flags in logs. Inspect network traffic for MCP stdio mode interactions with git_log, git_diff, or git_show tools using unvalidated ref/object parameters.

Impact Analysis

An attacker could exploit this to write files to any writable location on the system where the git-mcp-server process has access. This could lead to unauthorized file creation, data exfiltration, or system compromise depending on the server's permissions and configuration.

Compliance Impact

This vulnerability could lead to unauthorized file writes, potentially violating data integrity and confidentiality requirements under GDPR and HIPAA. It may result in unauthorized access to sensitive data or system files, leading to compliance breaches and regulatory penalties.

Mitigation Strategies

Upgrade to a patched version of git-mcp-server (2.15.3 or later). Implement input validation to reject parameters starting with dashes. Disable MCP stdio mode if not required. Apply strict scope and authentication checks for all tools.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85626. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart