How severe is GHSA-q66q-fx2p-7w4m?

No CVSS score has been assigned to GHSA-q66q-fx2p-7w4m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q66q-fx2p-7w4m?

GHSA-q66q-fx2p-7w4m affects the following packages: @modelcontextprotocol/server-filesystem (npm), @modelcontextprotocol/server-filesystem (npm). Ecosystems affected: npm.

How do I fix GHSA-q66q-fx2p-7w4m?

No patched version of @modelcontextprotocol/server-filesystem has shipped for GHSA-q66q-fx2p-7w4m 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 GHSA-q66q-fx2p-7w4m 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 GHSA-q66q-fx2p-7w4m 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 GHSA-q66q-fx2p-7w4m?

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

Is GHSA-q66q-fx2p-7w4m actively exploited in the wild?

No public exploit code has been indexed for GHSA-q66q-fx2p-7w4m 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 GHSA-q66q-fx2p-7w4m?

GHSA-q66q-fx2p-7w4m has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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 GHSA-q66q-fx2p-7w4m?

GHSA-q66q-fx2p-7w4m is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q66q-fx2p-7w4m published, and has it been updated?

GHSA-q66q-fx2p-7w4m was published on July 1, 2025 and was last updated on July 2, 2025. 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

GHSA-q66q-fx2p-7w4m — @modelcontextprotocol/ser…

Fix: modelcontextprotocol/servers@d00c60d

GHSA-q66q-fx2p-7w4m is a CWE-59 vulnerability in @modelcontextprotocol/server-filesystem. A fix is available for @modelcontextprotocol/server-filesystem — see the affected versions and patch details below.

@modelcontextprotocol/server-filesystem allows for path validation bypass via prefix matching and symlink handling

Also known asCVE-2025-53109

Published

Jul 1, 2025

Updated

Jul 2, 2025

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 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 GHSA-q66q-fx2p-7w4m.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% 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

563Kdownloads / week

Description

Versions of Filesystem prior to 0.6.3 & 2025.7.1 could allow access to unintended files via symlinks within allowed directories. Users are advised to upgrade to 2025.7.1 to resolve.

Thank you to Elad Beber (Cymulate) for reporting these issues.

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 GHSA-q66q-fx2p-7w4m 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 GHSA-q66q-fx2p-7w4m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q66q-fx2p-7w4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of Filesystem prior to 0.6.3 & 2025.7.1 could allow access to unintended files via symlinks within allowed directories. Users are advised to upgrade to 2025.7.1 to resolve. Thank you to Elad Beber (Cymulate) for reporting these issues.

O3 Security · Impact-Aware SCA

Is GHSA-q66q-fx2p-7w4m in your dependencies?

O3 Security finds GHSA-q66q-fx2p-7w4m 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