A read-only git_status could run a program. Six fixes landed in three MCP servers.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On 11 November 2026 the MCP reference servers fixed six vulnerabilities in the git, filesystem and fetch servers. The worst, GHSA-6hqx-gqrx-c5r2 (High, CVSS 7.8), let a repository's own Git config, such as core.fsmonitor, run a program through tools like git_status. The fixes ship in mcp-server-git and mcp-server-fetch 2026.11.11 and server-filesystem 2.3.0.
Why it matters
An agent asks for the status of a repo it was just handed. One line in that repo's .git/config, and a program runs with your server's permissions, and no write tool was ever called. The advisory lists no workaround other than upgrading.
What to do
Upgrade to mcp-server-git 2026.11.11 today. If you run server-filesystem on a date-style version, install @2.3.0 explicitly, and until then point the git server only at repos whose .git folder you trust.

My take
Lior Aharonov
Founder, 7IT Solutions
Read-only is a promise about your tools, not about the data they read. Treat every repo an agent hands you as hostile input.
I've seen this before
I've seen this movie before. In April 2022 Git itself patched CVE-2022-24765, where a planted .git directory could make Git run commands through settings like core.fsmonitor. Same knob, four years later, now behind an agent.
GitHub Blog: Git security vulnerability announced (April 2022) github.blog
Sources
Researched with AI tools; every fact is checked against the linked sources.