Two harden_repo flaws in MCP git server let repositories run commands via git drivers
Article Content
- •Repository-defined git filter and merge drivers can execute commands through the MCP git server's read-only and merge tool calls, per the advisories.
- •The first flaw uses a missing [include] path so drivers are not blanked at open time and are later triggered during git merge --abort.
- •The second flaw affects drivers with empty names (e.g. [filter ""]) because the detection pattern never matches them, per the second advisory, which cites version 2026.11.11.
- •The advisories describe the affected server as running commands as the user running the server.
- •No CVE identifiers, patches or in-the-wild exploitation are mentioned in the provided advisory text.
Two GitHub security advisories for the modelcontextprotocol/servers git server describe flaws in its harden_repo defence, which is meant to blank repository-defined filter and merge drivers so a repository cannot run programs. The first advisory (GHSA-9vjp-x34c-xg6v) says harden_repo reads drivers only once when a repository is opened, so a repository can use an [include] pointing to a file that does not yet exist; git silently ignores the missing include, nothing is blanked, and a later git_merge that adds that file brings in a filter definition that then runs when git merge --abort restores the repository. The advisory states the tool still reports that the merge was aborted and the repository is unchanged. The second advisory (GHSA-pm7p-vphh-2cg7) says the pattern used to collect driver names requires at least one character between dots, so drivers with an empty name, written as [filter ""], are never blanked; .gitattributes can select them with filter= or merge=. It says this affects version 2026.11.11 and that a repository can run a command of its choosing, as the user running the server, from a read-only tool call. The advisories describe the fix approach as sound apart from the pattern. No CVE identifiers, patch versions or exploitation reports appear in the provided text, and both are published as GitHub advisories on 2026-11-21.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
Common questions
Am I affected if I run the MCP git server on untrusted repositories?
Is there a known exploit in the wild?
What should defenders do first?
Continue Reading
Lazarus Group Targets 30 South Korean Servers Using PHP Vulnerabilities North Korea-linked Lazarus Group has targeted 30 servers in South Korea as part of a larger cyber operation involving 581 servers across 10 countries. The attacks exploit two critical remote code execution vulnerabilities in PHP (CVE-2026-109618 and CVE-2026-109619), allowing unauthorized server command execution. The…