CVE-2025-53110 — @modelcontextprotocol/ser…
Fix: modelcontextprotocol/servers@cc99bdaCVE-2025-53110 is a Path Traversal vulnerability in @modelcontextprotocol/server-filesystem. A fix is available for @modelcontextprotocol/server-filesystem — see the affected versions and patch details below.
Model Context Protocol Servers Vulnerable to Path Validation Bypass via Colliding Path Prefix
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-53110.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@modelcontextprotocol/server-filesystemnpmDescription
Model Context Protocol Servers is a collection of reference implementations for the model context protocol (MCP). Versions of Filesystem prior to 0.6.4 or 2025.7.01 could allow access to unintended files in cases where the prefix matches an allowed directory. Users are advised to upgrade to 0.6.4 or 2025.7.01 resolve.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @modelcontextprotocol/server-filesystem | all versions | No fix |
| 📦npm | @modelcontextprotocol/server-filesystem | ≥ 2025.1.14&&< 2025.7.1 | 2025.7.1npm install @modelcontextprotocol/server-filesystem@2025.7.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @modelcontextprotocol/server-filesystem, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2025-53110; check the affected-versions list above or the advisory for the patched release of @modelcontextprotocol/server-filesystem, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2025-53110 in your dependencies?
Find it across npm, including transitive dependencies.