MCP Servers v2.1.0 Fixes Vulnerabilities in Filesystem and Fetch
MCP Servers v2.1.0 lists fixes for filesystem path checks and fetch destination validation. Check affected package versions and the Windows caveat in the upstream release before upgrading.
- Announcement
- Oct 25, 2026
- Reported here
- Oct 28, 2026
Filesystem containment and a Windows caveat
The October 25 release lists eight vulnerabilities across three servers. For filesystem, it addresses cases where symlink or path handling could let operations escape an allowed directory. Version 2.0.1 fixes the listed package ranges; the upstream advisory says the Windows write-path fix is partial.
Fetch checks the connection destination
Fetch now checks the host it connects to, treats private IPv4 addresses embedded in NAT64 addresses as private, and checks robots.txt after redirects. The release lists versions through 2026.10.19 as affected and 2026.10.24 as fixed.
Check installed versions before changing them
Filesystem installations on date-based versions may need an explicit 2.0.1 install because package managers can rank those dates higher. Read the linked advisories for your version and platform; the release does not establish that every installation is exposed.
Go to the source.
Official announcements are the basis for this report. They describe the providers’ claims; they aren’t independent performance tests.