# CVE-2025-53110: Model Context Protocol Servers Vulnerable to Path Validation Bypass via Colliding Path Prefix

> Attackers can bypass path validation to access unintended files in the Model Context Protocol filesystem server.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Jul 2025
- **Updated:** 2 Jul 2025
- **Also known as:** GHSA-hc55-p739-j48w

## What is CVE-2025-53110?

CVE-2025-53110 is a high-severity path traversal vulnerability in modelcontextprotocol servers, published on 2 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-53110?

4 open source packages ship an affected version, including @modelcontextprotocol/server-filesystem.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@modelcontextprotocol/server-filesystem` | npm | All versions to 0.6.2 | None |
| `@modelcontextprotocol/server-filesystem` | npm | All versions to 0.6.2 | None |
| `@modelcontextprotocol/server-filesystem` | npm | From 2025.1.14 | 2025.7.1 |
| `@modelcontextprotocol/server-filesystem` | npm | From 2025.1.14 | 2025.7.1 |

## How do I fix CVE-2025-53110?

Upgrade @modelcontextprotocol/server-filesystem to 2025.7.1 or later.

## Is CVE-2025-53110 being exploited?

There is no known exploitation of CVE-2025-53110 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53110 and fix it if it is affected.

What it is: CVE-2025-53110 is a high-severity path traversal vulnerability in modelcontextprotocol servers, published on 2 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-53110 in the wild and no public exploit code.

Affected packages and fixed versions:
- @modelcontextprotocol/server-filesystem (npm): affected all versions up to 0.6.2; no fix listed
- @modelcontextprotocol/server-filesystem (npm): affected all versions up to 0.6.2; no fix listed
- @modelcontextprotocol/server-filesystem (npm): affected from 2025.1.14; fixed in 2025.7.1
- @modelcontextprotocol/server-filesystem (npm): affected from 2025.1.14; fixed in 2025.7.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53110/ (Markdown: https://insights.sbomify.com/CVE-2025-53110/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53110
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53110
- OSV: https://osv.dev/vulnerability/CVE-2025-53110

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53110/
Summaries are generated and may contain mistakes; the official description above is the record.