The Model Context Protocol (MCP) reference-server v2.5.0 release introduces security updates across three distinct server packages. These updates strengthen security boundaries within the Git, filesystem, and everything servers. This guidance provides a technical overview of the necessary upgrades and the specific mechanics of the addressed vulnerabilities.
Package Upgrade Requirements
Operators should verify their current versions against the following affected and fixed ranges:
- mcp-server-git: Affected through 2026.11.11; fixed in 2026.11.18.
- @modelcontextprotocol/server-filesystem: Affected in all versions before 2.4.0 and date versions 2025.1.14 through 2026.8.31; fixed in 2.4.0.
- @modelcontextprotocol/server-everything: Affected through 2.3.0; fixed in 2.3.1.
A specific upgrade challenge exists for the filesystem package. Because the project previously used date-based versioning (e.g., 2025.x, 2026.x) and transitioned to semantic versioning at 1.0.0, package managers rank the new 2.4.0 version below every 2025.x and 2026.x version. Consequently, these will not be offered as automatic upgrades for installations using date-based versioning. To update, users must run: npm install @modelcontextprotocol/server-filesystem@2.4.0.
Git Server Security Mechanics
The release addresses six Git-related advisories by tightening how the server interacts with repository configurations:
- Maintenance and Garbage Collection: Previously, successful merges could trigger automatic maintenance and a repository’s
gc.recentObjectsHook, potentially executing hooks with server privileges. The update setsmaintenance.auto=falseandgc.auto=0for all Git commands. (Maintenance fix) - Lazy Fetching: Lazy fetching is the process of retrieving missing objects on demand. Previously, repository configuration could cause a read-only Git tool to start a program during this process. The server now sets
GIT_NO_LAZY_FETCH=1and rejects promisor remotes if the Git version is too old to support this flag. (Fetch fix) - Driver Hardening: An included configuration file could be created by a merge or checkout and activate a filter or merge driver on a subsequent Git process. The server now rereads drivers before executing Git commands. Note that the
--repositoryconfinement check is not yet repeated after such a write. (Driver fix) - Empty-Name Drivers: Git accepts an empty driver name, which could be exploited. The server now explicitly clears empty-name filter and merge drivers. (Empty-name fix)
- Index Path Validation: A crafted index entry outside the working tree could make read-only diff tools return file contents and
git_statusdisclose path existence under--repository. The server now validates index paths and disables the untracked cache. (Index fix) - Submodule Configuration: Submodule configuration could run programs in nested operations. The update forces
diff.submodule=short, overrides drivers, and refuses Git versions older than 2.33 for repositories with checked-out submodules. (Submodule fix)
Filesystem and Everything Server Fixes
The filesystem server update addresses a vulnerability where directory listing functions—specifically list_directory, list_directory_with_sizes, directory_tree, and search_files—could follow a symlink swap. A symlink swap occurs when a directory is replaced by a symbolic link after validation, potentially returning entries outside the intended scope. The fix anchors these listings on Linux and macOS; however, the release notes specify that listings are not yet anchored on Windows.
The everything server fix addresses a NAT64-related issue. NAT64 is a mechanism that allows IPv6-only networks to communicate with IPv4-only servers. Previously, the gzip-file-as-resource feature treated certain IPv6 addresses in the 64:ff9b::/96 range as public, which could allow a URL to reach a private IPv4 address when using a NAT64 gateway. The update now correctly validates the embedded IPv4 address.
