Vulnerability in @wonderwhy-er/desktop-commander (CVE-2026-10691)
Summary
Vulnerability in @wonderwhy-er/desktop-commander (CVE-2026-10691). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.2.39 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10691 has been found in @wonderwhy-er/desktop-commander.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade @wonderwhy-er/desktop-commander to 0.2.39 or later.
If unsure, ask your IT team or search "@wonderwhy-er/desktop-commander CVE-2026-10691" on the vendor's site.
CVE-2026-10691 (@wonderwhy-er/desktop-commander) — CWE-400 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.2.39 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in @wonderwhy-er/desktop-commander.
Check the vendor advisory for the affected versions of @wonderwhy-er/desktop-commander.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.2.39.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@wonderwhy-er/desktop-commander' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@wonderwhy-er/desktop-commander' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@wonderwhy-er/desktop-commanderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @wonderwhy-er/desktop-commander to 0.2.39ステージング環境で 0.2.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com