Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Patch your MCP reference servers now

Written November 12, 2026

Six advisories in one release: the Git server runs commands from a repo's own config on read-only calls. The fixes are out now.

The verdict

Update now. The worst bug in this release needs only a read-only Git call against a hostile repository, and the fix is a version bump for three packages.

What v2.4.0 fixes

The v2.4.0 release of the MCP reference servers fixes six vulnerabilities in three servers. The fixed versions differ by package: @modelcontextprotocol/server-filesystem goes to 2.3.0, and mcp-server-git and mcp-server-fetch go to 2026.11.11.

Git: a repository's own config ran commands

A read-only call such as git_status on an untrusted repository used to run a command named in that repository's .git/config — through core.fsmonitor, diff.external, hooks, filter and merge drivers, or signing settings — with the server's privileges. The advisory rates this High, at CVSS 7.0, and notes that the payload can sit inline in the config line itself. Every Git command now overrides those settings, and a Git older than 2.31, which would ignore the overrides, is refused. The second Git fix closes a confinement gap: a repository inside the allowed one could read another repository's objects through alternate object stores, pass off a linked worktree's Git directory as the allowed repository's, or follow a symlink in a Git directory to outside the allowed repository. On Windows, a directory junction is not yet covered.

Filesystem: the file could change after the check

Two race fixes. The read tools and file resources now open a file relative to the directory that was checked, so a directory swapped for a symlink between the access check and the read can no longer return a file from outside the allowed directories, and a FIFO, socket, or device is refused rather than read. On Windows this narrows the race without closing it. And move_file now takes the source out of its own checked directory under a fresh name first, so a swapped source directory can no longer bring an outside file into the allowed directories, where it would become readable.

Fetch: two ways past the guards

The private-address guard read the IPv6 site-local range fec0::/10 as public. The advisory calls this a classifier gap and rates it Low, because a stock host usually has no route to those addresses; the fix refuses that range and any IPv6 address outside global unicast that does not carry an IPv4 address. Separately, robots.txt rules are now matched against the path the site will resolve as well as the path as written, so //private or /x/../private can no longer slip past a Disallow: /private rule.

The two upgrade traps

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: MCP reference servers 2.3.0: what's new · AWS MCP server let deny lists silently fail · A malicious MCP server probed cloud credentials · Two MCP packages on npm were stealing secrets