Vibeleaderboard
← All Intel
Intel / repo

servers v2.5.0

Source
github.com
Author
cliffhall
Date

Context

Version v2.5.0 of the 's reference servers, the official example servers that let an AI application work with Git repositories, files and the web through a standard interface, fixes eight vulnerabilities in three servers. Six are in mcp-server-git, and five of those share one cause. A repository is more than its files: its .git directory holds configuration that can name programs for Git to run. Whoever supplies the repository, for example as an archive or a shared folder, controls that configuration, and when an points the server at it, Git can run those programs with the server's privileges.

Two of the advisories show how little the attacker needs. In GHSA-h2g3-rwxm-xfm3, rated High, a successful git_merge ended with Git's automatic maintenance, whose garbage collection runs a command named by the repository's own gc.recentObjectsHook setting; the advisory describes the result as command execution as the server user "from repository contents alone," and notes the model might make the call after reading instructions in the repository. In GHSA-87qg-cmw8-jc5m, scored 7.8 out of 10, read-only tools such as git_show and git_diff could make Git fetch a missing object by starting a program the repository's configuration named, before any network connection, so the attacker needed neither a reachable server nor credentials. The fixes switch automatic maintenance off and stop Git from fetching objects on its own. A third, GHSA-r2q8-f657-4r56, let a crafted index file make git_diff return the contents of files outside the repository the server was confined to.

This is the second week running that the Git server has closed this kind of hole. The previous release overrode settings such as core.fsmonitor, diff.external, hooks and filter drivers so that a read-only call on an untrusted repository could no longer run a program; v2.5.0 fixes settings that list missed, including a driver with an empty name. Each fix closes one path, and the release notes say others remain open: the check that confines the server to its --repository directory is not yet repeated after a merge or checkout writes new files, and on Windows the filesystem server's directory listings are not yet protected against a folder being swapped for a link. The 87qg advisory's own workaround is not to open repositories received as archives or shared folders, and running the server as a user without valuable credentials limits the damage when a fix misses something.

The upgrades are mcp-server-git 2026.11.18, @modelcontextprotocol/server-filesystem 2.4.0 and @modelcontextprotocol/server-everything 2.3.1. Users of the filesystem server on an older date-style version such as 2026.8.31 will not be offered the fix automatically, because npm ranks 2.4.0 below every 2025.x and 2026.x version; the release notes say to install 2.4.0 explicitly. The filesystem flaw itself is minor by comparison, rated Low in its advisory: winning a timing race could reveal the names of files outside the allowed directories, not their contents.

Key takeaways · AI-distilled
  • In mcp-server-git, any successful git_merge, fast-forwards included, ended in `git maintenance run --auto`, whose garbage collection runs the command a repository's own gc.recentObjectsHook names. 2026.11.18 sets maintenance.auto=false and gc.auto=0 for every Git command.
  • With --repository set, a crafted .git/index naming a path such as ../outside/secret made git_diff and git_diff_unstaged return that outside file's content. The server now checks the index before any tool reads it and turns off the untracked cache.
  • Two gaps remain open per the release notes: mcp-server-git does not yet repeat its --repository confinement check after a merge or checkout writes the tree (#5599), and server-filesystem directory listings are not yet anchored against symlink swaps on Windows (#5600).
  • Package managers rank server-filesystem 2.4.0 below the old 2025.x and 2026.x date versions, so they will not offer it as an upgrade. Anyone on a date-versioned release has to install @modelcontextprotocol/server-filesystem@2.4.0 explicitly.
  • server-everything's private-address guard read NAT64 addresses (64:ff9b::/96) as public, so on a network with a NAT64 gateway the gzip-file-as-resource tool could reach a private IPv4 address. 2.3.1 checks the embedded IPv4 address instead.
Terms in this piece · Glossary
  • MCP — The Model Context Protocol — an open standard that lets any AI assistant plug into any tool or data source without custom integration code.
  • AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
More from cliffhall
Recommended reads
Comments

Checking sign-in…

Loading comments…