Skip to content
MCP Reference-Server v2.5.0 Patches Eight Vulnerabilities in Git, Filesystem and Everything Servers

MCP Reference-Server v2.5.0 Patches Eight Vulnerabilities in Git, Filesystem and Everything Servers

First seen 21 Nov 2026, 20:17 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 21, 2026 at 20:17 UTC
  • •Eight vulnerabilities are fixed across the mcp-server-git, server-filesystem, and server-everything packages in MCP reference-server v2.5.0.
  • •The filesystem package's 2.4.0 release will not be offered as an automatic upgrade to installations using date-based versions, so it must be installed manually.
  • •Git fixes address hooks that could run with server privileges, programs launched during lazy fetching, and crafted index entries that expose file contents or path existence.
  • •The articles report no confirmed exploitation in the wild and list no CVE identifiers.

The Model Context Protocol (MCP) reference-server v2.5.0 release includes security updates to three server packages: mcp-server-git, @modelcontextprotocol/server-filesystem, and @modelcontextprotocol/server-everything. Both articles describe eight vulnerabilities, six of which are Git-related advisories concerning repository configuration handling. For mcp-server-git, versions through 2026.11.11 are affected and the fix is in 2026.11.18. For server-filesystem, all versions before 2.4.0 and date versions 2025.1.14 through 2026.8.31 are affected, with the fix in 2.4.0. For server-everything, versions through 2.3.0 are affected and the fix is in 2.3.1. The Git fixes disable automatic maintenance and garbage collection hooks, set GIT_NO_LAZY_FETCH=1 to stop read-only tools from launching programs during lazy fetching, reread filter and merge drivers before running Git commands, clear empty-name drivers, validate index paths, and force diff.submodule=short with a Git version floor of 2.33 for submodule repositories. Because package managers rank 2.4.0 below date-based 2025.x and 2026.x versions, the filesystem upgrade is not offered automatically and must be installed explicitly with npm. The articles do not report exploitation in the wild, and neither assigns CVE identifiers to the issues.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-11-18
mcp-server-git fixed version released
mcp-server-git 2026.11.18 is the fixed release for versions affected through 2026.11.11.
Tech.Yahoo
2026-11-21
MCP reference-server v2.5.0 security updates announced
The v2.5.0 release covering three server packages and eight vulnerabilities was reported by both articles.
Forkast.News

More articles in this cluster (5)

Common questions

Am I affected if I run the MCP filesystem server?
Installations on any version before 2.4.0, and on date versions 2025.1.14 through 2026.8.31, are affected according to the articles. Check your installed version against these ranges.
Why won't npm update the filesystem package automatically?
Package managers rank semantic version 2.4.0 below date-based 2025.x and 2026.x versions, so it is not offered as an upgrade. You must install it explicitly with npm install @modelcontextprotocol/[email protected].
Is there evidence these flaws are being exploited?
Neither article reports exploitation in the wild, and no CVE identifiers are given for these issues.