# CVE-2025-11489: wonderwhy-er DesktopCommanderMCP filesystem.ts isPathAllowed symlink

> Local attackers can bypass path restrictions via symlink following in Desktop Commander MCP, potentially accessing or modifying unauthorized files.

- **Severity:** Low 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 23 Oct 2025
- **Also known as:** GHSA-2jf9-5hf7-r448

## What is CVE-2025-11489?

CVE-2025-11489 is a low-severity path traversal vulnerability in wonderwhy-er DesktopCommanderMCP, published on 8 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following), CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Wonderwhy-Er Desktopcommandermcp.

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

No fix has been published for CVE-2025-11489 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11489 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11489 exists.

## Other vulnerabilities in wonderwhy-er DesktopCommanderMCP

- [CVE-2025-11490](https://insights.sbomify.com/CVE-2025-11490/): wonderwhy-er DesktopCommanderMCP Absolute Path command-manager.ts extractBaseCommand os command injection (medium 5.3)
- [CVE-2025-11491](https://insights.sbomify.com/CVE-2025-11491/): wonderwhy-er DesktopCommanderMCP command-manager.ts CommandManager os command injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11489 is a low-severity path traversal vulnerability in wonderwhy-er DesktopCommanderMCP, published on 8 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11489 exists.

Affected product: wonderwhy-er DesktopCommanderMCP. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-11489/ (Markdown: https://insights.sbomify.com/CVE-2025-11489/index.md)
```

## Sources

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

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