7IT Solutions
7MapsOverviewLive chartStateReliableMethodologyVerifyFor agentsFor ownersNews

The official MCP filesystem server got two path fixes. Your update may not fetch them.

By Lior AharonovFounder, 7IT Solutions ·

What happened

On 25 October the official MCP servers repo published 8 advisories, 3 Moderate and 5 Low. Two hit server-filesystem: a trailing quote or space slipped past the path check, and on macOS and Windows a different letter case got past the symlink check. Both are fixed in 2.0.1.

Why it matters

Here is the trap. Your install says 2026.8.31, the fix says 2.0.1, and the advisories warn package managers may not offer it as an upgrade. You run the update, nothing moves, and you believe you are patched.

What to do

Run npm ls @modelcontextprotocol/server-filesystem today. If it shows a 2025.x or 2026.x version, install 2.0.1 by name, as the advisories say, and pin it.

My take

Lior Aharonov
Founder, 7IT Solutions

"I updated" and "I'm patched" used to mean the same thing. Check the version you are running, not the command you ran.

Sources

modelcontextprotocol/servers security advisoriesgithub.com
GHSA-7rgq-gccq-qphx: path traversal in server-filesystemgithub.com
GHSA-4gxg-m5jx-9j57: case-variant path bypasses symlink checkgithub.com
npm registry: @modelcontextprotocol/server-filesystemregistry.npmjs.org
mcpsecurityfilesystemversioning

Researched with AI tools; every fact is checked against the linked sources.

7Maps news

Every 7Maps day is signed and chained to the day before.Verify in your browser