MCP Reference Server Security Update: Versions and Upgrade Steps
The official reference servers v2.4.0 release, published on November 11, fixes six vulnerabilities across Filesystem, Git and Fetch: one High, three Moderate and two Low. Upgrade the package your host actually starts, then restart it and verify a read-only call. This is a reference-server release, separate from the MCP protocol revision.
The minimum corrected versions for these advisories are Filesystem 2.3.0, Git 2026.11.11 and Fetch 2026.11.11. The repository tag v2.4.0 is not an installable version shared by all three packages. Facts and fixed-tag instructions were checked on November 17, 2026; a later release needs its own review.
What is affected?
| Package and advisory | Severity | Affected versions | Fixed version and change |
|---|---|---|---|
@modelcontextprotocol/server-filesystem: GHSA-p9cv-8g75-4xcg | Moderate | Before 2.3.0, plus date versions 2025.1.14 through 2026.8.31 | 2.3.0: keep reads anchored to the checked directory during a symlink race |
| Same package: GHSA-7m4x-rv66-mxhh | Moderate | Same range | 2.3.0: anchor the source of a move so a directory swap cannot move an outside file into the allowed tree |
mcp-server-git: GHSA-6hqx-gqrx-c5r2 | High | Before 2026.11.11 | 2026.11.11: override repository configuration that could run external programs, even during a read-only operation |
| Same package: GHSA-q74p-4wrc-q7w6 | Moderate | >=2026.10.28, <2026.11.11 | 2026.11.11: reject escapes through alternates, linked worktrees and symlinked Git directories |
mcp-server-fetch: GHSA-3rxj-6jhw-qfv7 | Low | >=2026.10.10, <2026.11.11 | 2026.11.11: correct the public-address classification of fec0::/10 |
| Same package: GHSA-f9hh-cmx9-2f23 | Low | >=0.6.1, <2026.11.11 | 2026.11.11: normalize paths consistently when applying robots.txt rules |
An older version falling outside one advisory’s range is not necessarily safe from other advisories. The Git issue means that merely disabling write tools or setting --repository did not prevent repository-controlled execution. The Fetch address advisory does not establish a working cloud-metadata exploit; the robots.txt issue concerns crawling policy, not an authentication bypass or arbitrary code execution.
1. Identify the process your host launches
Check the server entry’s command, arguments, working directory and executable path locally. A project npm dependency, global npm package, npx invocation, Python virtual environment, uvx environment and container can all resolve to different code. Updating one does not update the others. Do not share a full client configuration or environment dump to check a version.
| Launch method | Inspect | Update the same target |
|---|---|---|
| Project npm dependency | Run npm ls @modelcontextprotocol/server-filesystem in the launcher’s project | Install the explicit version in that project; retain its lockfile |
| Global npm executable | npm ls -g @modelcontextprotocol/server-filesystem; confirm which executable the host uses | Use the global install command only if this is the actual launch method |
npx | Read the package argument in the host configuration | Pin the package in that entry; a project or global upgrade does not rewrite it |
| Python module / pip | Run package metadata commands with the launcher’s Python interpreter | Install in that interpreter’s environment |
uvx / uv tool | Inspect the exact pinned uvx argument, or uv tool list for an installed tool | Change the uvx package pin, or reinstall the named uv tool; pip in another environment has no effect |
| Docker / source checkout | Record the actual image digest / source revision and the package and Git versions inside it | Use a traceable corrected build and recreate the container; do not infer the contents from latest |
2. Pin the corrected package
Filesystem: npm and npx
For a project dependency, run this in the project that launches the server:
npm install @modelcontextprotocol/[email protected]
npm ls @modelcontextprotocol/server-filesystemFor a global installation, the corresponding command is npm install -g @modelcontextprotocol/[email protected]; check it with npm ls -g @modelcontextprotocol/server-filesystem. Use it only when your host actually launches that global executable.
The date-version trap: npm orders versions such as 2026.8.31 above 2.3.0. A generic update may retain the affected date version. The explicit @2.3.0 pin follows the release’s migration instructions.
For an npx-based host entry, preserve your real allowed directories and use this package argument:
{
"command": "npx",
"args": ["-y", "@modelcontextprotocol/[email protected]", "/absolute/path/to/allowed-directory"]
}Replace the directory before use. Start with a dedicated test directory containing a harmless text file; keep sensitive files outside it. Merge the entry into your host’s configuration format rather than replacing the whole file.
Git and Fetch: Python environments
Run these commands with the same interpreter the host launches, for example the absolute Python path of its virtual environment:
python -m pip show mcp-server-git mcp-server-fetch
python -m pip install --upgrade mcp-server-git==2026.11.11 mcp-server-fetch==2026.11.11
python -c 'from importlib.metadata import version; print("git", version("mcp-server-git")); print("fetch", version("mcp-server-fetch"))'
git --versionIf that interpreter does not have pip, use its environment manager to install these same pins. Installing both packages is only necessary when you use both. The fixed Git server requires Git 2.31 or newer and refuses tool calls with an older Git.
For uvx, pin each server in the actual host entry. Git, for example:
{
"command": "uvx",
"args": ["mcp-server-git==2026.11.11", "--repository", "/absolute/path/to/test-repository"]
}Fetch uses "args": ["mcp-server-fetch==2026.11.11"]. Check package metadata in the selected uvx environments, rather than the system Python:
uvx --from mcp-server-git==2026.11.11 python -c 'from importlib.metadata import version; print(version("mcp-server-git"))'
uvx --from mcp-server-fetch==2026.11.11 python -c 'from importlib.metadata import version; print(version("mcp-server-fetch"))'For tools installed with uv tool, inspect uv tool list; explicit reinstall examples are uv tool install --force mcp-server-git==2026.11.11 and uv tool install --force mcp-server-fetch==2026.11.11. Preserve any existing tool-specific interpreter and dependency options. These are separate installations from uvx.
For Docker or a source build, consult the fixed-tag Git, Fetch and Filesystem instructions. Check the built package versions and Git inside the actual runtime; no dated Docker tag is assumed here.
3. Restart and verify a read-only operation
Save a local backup of the entry you change. Stop the old server and restart the host or its MCP connection so a pre-upgrade process cannot keep serving requests. Use the Inspector guide to connect with the exact configured command and list tools. Do not assume every server implements a --version flag: confirm the package metadata in the launching environment as well.
| Server | Harmless positive check | Boundary check |
|---|---|---|
| Filesystem | Read a known test file inside the allowed directory | Ask to read a harmless test file outside that directory; it must be denied |
| Git | Call git_status on a disposable repository you created | Ask for status on a separate disposable repository outside --repository; it must be denied |
| Fetch | Fetch a URL you control and check the expected text | Use a controlled fixture for robots / address-policy cases; never probe a real metadata service to test an advisory |
Successful installation or tool listing establishes only part of the upgrade chain. A normal read and a boundary rejection do not reproduce a symlink race, malicious Git configuration or either Fetch advisory. Keep vulnerability regression claims separate from these smoke checks.
If a server fails, leave that server disabled while checking the interpreter, package pin, executable path, Git version and stale process. Restoring a configuration backup must not silently re-enable a known-vulnerable package.
Residual limits and verification scope
On Windows, the Filesystem changes narrow the directory race without eliminating it; the Git fix does not cover directory junctions. The Git configuration fix targets untrusted repository-level settings, not every trusted global setting. Where untrusted users can modify the underlying tree, continue to use an appropriately restricted runtime and account. An allowed-directory setting alone is not a complete sandbox.
Verified on November 17, 2026 with macOS 26.6.2 arm64, Python 3.11.12, Node.js 26.13.0, Git 2.54.0 and Python MCP SDK 2.3.0. The pinned Filesystem, Git and Fetch packages each initialized and listed tools over stdio, negotiating protocol 2025-11-25. All seven smoke checks passed: allowed file read / outside-directory rejection; repository status / outside-repository rejection; controlled Fetch success / robots rejection / default private-address rejection. The Fetch positive fixture explicitly allowed loopback; the default-policy rejection used a separate server instance. These checks do not establish that all six vulnerabilities are fixed in every environment.
Filesystem ran from a local npm project package; Git and Fetch ran with the isolated environment’s Python modules. Both uvx package-metadata commands above were also run successfully. The npx and uvx host-launch examples, global npm installation, literal pip install command, uv tool reinstallation, Docker, source builds and Windows were not run as part of this check. No existing user MCP configuration was upgraded.
For protocol-level authentication and transport requirements, continue with MCP server best practices. The local server security guide covers the surrounding host permissions.