# MCP filesystem, git and fetch servers: update now

> MCP servers v2.4.0, released 2026-11-11, fixes six vulnerabilities in the filesystem, git and fetch servers. Fixed versions: filesystem 2.3.0, git and fetch 2026.11.11.

- Published: 2026-11-11
- Publisher: Rig Labs (https://riglabs.ai/)
- Canonical: https://riglabs.ai/blog/mcp-servers-security-update/
- Answers: mcp servers security update
- Agent file (a short card for your agent): https://riglabs.ai/blog/mcp-servers-security-update/AGENT.md

---

The Model Context Protocol project released MCP servers v2.4.0 on November 11, 2026, fixing six vulnerabilities in three of its reference servers: filesystem, git and fetch. The fixed versions are `@modelcontextprotocol/server-filesystem` 2.3.0, `mcp-server-git` 2026.11.11 and `mcp-server-fetch` 2026.11.11, per the [release notes](https://github.com/modelcontextprotocol/servers/releases/tag/v2.4.0).

What you can now do: if Claude, Cursor or another agent reads your files, your code repositories or web pages through one of these three servers (MCP servers are the small programs that give an agent a tool), a version change closes six ways a bad file, repository or web page could reach past the limits you set.

## Which MCP servers are affected?

Three MCP reference servers are affected, per the release notes:

| Server | Affected versions | Fixed in |
|---|---|---|
| `@modelcontextprotocol/server-filesystem` | All before 2.3.0, and date versions 2025.1.14 through 2026.8.31 | 2.3.0 |
| `mcp-server-git` | Through 2026.11.4 | 2026.11.11 |
| `mcp-server-fetch` | Through 2026.11.4 | 2026.11.11 |

## What could go wrong on the old versions?

The old versions of the MCP filesystem, git and fetch servers each had two holes, per the release notes:

- **Filesystem.** The read tools could return a file from outside the folders you allowed, if a folder was swapped for a link at the right moment (advisory GHSA-p9cv-8g75-4xcg). `move_file` could bring an outside file into the allowed folders the same way.
- **Git.** A read-only call such as `git_status` on an untrusted repository could run a program named in that repository's `.git/config`, with the server's rights (advisory GHSA-6hqx-gqrx-c5r2). The limit to the allowed repository could also be escaped through alternate object stores, linked worktrees or symlinks in the Git directory (advisory GHSA-q74p-4wrc-q7w6).
- **Fetch.** The guard that keeps the server away from private network addresses treated some IPv6 addresses as public, and robots.txt rules could be bypassed with paths like `//private`.

The git one matters most if your agent ever opens a repository you did not write: on the old version, looking at it was enough.

## What stays open after the update?

Two of the six fixes are partial on Windows, per the release notes. The filesystem read fix "narrows the race without closing it" on Windows, and the git fix does not yet cover directory junctions there. The fixed git server also refuses Git versions older than 2.31, because they would ignore the new protections.

## Why will you not get the filesystem fix automatically?

The filesystem fix needs an explicit install, because package managers rank version 2.3.0 below the older date versions (2025.x and 2026.x), per the release notes. If your setup runs a date version, asking for "latest" may not move you to 2.3.0.

## What to do today

Open the file where your agent's MCP servers are listed (in Claude Desktop: Settings > Developer > Edit Config) and look for `server-filesystem`, `mcp-server-git` and `mcp-server-fetch`. Pin each one you find to the fixed version, then restart the app:

```
@modelcontextprotocol/server-filesystem@2.3.0
mcp-server-git==2026.11.11
mcp-server-fetch==2026.11.11
```

If none of the three is in your config, there is nothing to do.

Last checked 2026-11-11.

Sources:
- [MCP servers v2.4.0 release notes, 2026-11-11](https://github.com/modelcontextprotocol/servers/releases/tag/v2.4.0)
