DesktopCommanderMCP is vulnerable to Uncontrolled Resource ConsumptionGHSA-r87g-78mx-3wg4
MEDIUMFix: wonderwhy-er/DesktopCommanderMCP#400GHSA-r87g-78mx-3wg4 is a medium-severity (CVSS 4.3) Uncontrolled Resource Consumption vulnerability in @wonderwhy-er/desktop-commander. A fix is available for @wonderwhy-er/desktop-commander — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-r87g-78mx-3wg4.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-r87g-78mx-3wg4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
@wonderwhy-er/desktop-commandernpmDescription
A security flaw has been discovered in wonderwhy-er DesktopCommanderMCP up to 0.2.38. This impacts an unknown function of the file src/search-manager.ts of the component start_search. Performing a manipulation of the argument SearchResult[] results in inefficient regular expression complexity. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 0.2.39 will fix this issue. The patch is named 4ce845f8749b6a159b57b38dcc3357f7222a8078. It is suggested to upgrade the affected component.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @wonderwhy-er/desktop-commander | all versions | 0.2.39npm install @wonderwhy-er/desktop-commander@0.2.39 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @wonderwhy-er/desktop-commander, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @wonderwhy-er/desktop-commander to 0.2.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r87g-78mx-3wg4 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-r87g-78mx-3wg4 in your dependencies?
Find it across npm, including transitive dependencies.