How severe is CVE-2025-53110?

No CVSS score has been assigned to CVE-2025-53110 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-53110?

CVE-2025-53110 affects the following packages: @modelcontextprotocol/server-filesystem (npm), @modelcontextprotocol/server-filesystem (npm). Ecosystems affected: npm.

How do I fix CVE-2025-53110?

No patched version of @modelcontextprotocol/server-filesystem has shipped for CVE-2025-53110 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2025-53110 in my npm dependencies?

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.

How do I mitigate CVE-2025-53110 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-53110?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-53110 can be triaged on real exposure rather than presence alone.

Is CVE-2025-53110 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-53110 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-53110?

CVE-2025-53110 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-53110?

CVE-2025-53110 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-53110 published, and has it been updated?

CVE-2025-53110 was published on July 2, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-53110 — @modelcontextprotocol/ser…

Fix: modelcontextprotocol/servers@cc99bda

CVE-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

Also known asGHSA-hc55-p739-j48w

Published

Jul 2, 2025

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

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.

41other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@modelcontextprotocol/server-filesystemnpm

711Kdownloads / week

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.

Affected Packages

2 total 1 fixed

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.1`npm install @modelcontextprotocol/server-filesystem@2025.7.1`

Detection & mitigation playbook

Open-source dependency

Detect
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
No patched version of @modelcontextprotocol/server-filesystem has shipped for CVE-2025-53110 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-53110 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-53110. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-53110 in your dependencies?

O3 Security finds CVE-2025-53110 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works