CVE-2025-11489 json
wonderwhy-er DesktopCommanderMCP filesystem.ts isPathAllowed symlink
published last yr. modified last mo. also EUVD-2025-33304
- cvss
- 4.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
A security vulnerability has been detected in wonderwhy-er DesktopCommanderMCP up to 0.2.13. This vulnerability affects the function isPathAllowed of the file src/tools/filesystem.ts. The manipulation leads to symlink following. The attack can only be performed from a local environment. The attack's complexity is rated as high. It is stated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. The vendor explains: "Our restriction features are designed as guardrails for LLMs to help them stay closer to what users want, rather than hardened security boundaries. (...) For users where security is a top priority, we continue to recommend using Desktop Commander with Docker, which provides actual isolation. (...) We'll keep this issue open for future consideration if we receive more user demand for improved restrictions." This vulnerability only affects products that are no longer supported by the maintainer.
Is CVE-2025-11489 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/219#issue-3343862329 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/219 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.0 | CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 4.5 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C |
| CNA | 3.0 | 4.5 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C |
| CNA | 2.0 | 3.5 | AV:L/AC:H/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:C |
| CNA | 4.0 | 1.1 | CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 4.5 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 2.0 | 3.5 | AV:L/AC:H/Au:S/C:P/I:P/A:P |
Affected products
- wonderwhy-er DesktopCommanderMCP
Classification
References
-
github.com
/wonderwhy-er/DesktopCommanderMCP/issues/219#issue-3343862329
exploit, issue-tracking, vendor-advisory
-
github.com
/wonderwhy-er/DesktopCommanderMCP/issues/219
issue-tracking, exploit, vendor-advisory
-
vuldb.com
/?id.327606
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.327606
signature, permissions-required, vdb-entry
-
vuldb.com
/?submit.668004
third-party-advisory, vdb-entry
-
github.com
/wonderwhy-er/DesktopCommanderMCP/issues/219#issuecomment-3214114903
issue-tracking
Sources
- CVE List CVE-2025-11489
- NVD CVE-2025-11489
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.