CVE-2026-10691

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-06-03. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
27.9%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

Advisory Details (5)

Auto-updated Jun 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github_commit, github_pr.
github_release Patch Available

Release Notes - v0.2.39

Patch available: wonderwhy-er/DesktopCommanderMCP v0.2.39

https://github.com/wonderwhy-er/DesktopCommanderMCP/releases/tag/v0.2.39
github_pr Patch Available

fix(security): validate regex patterns to prevent ReDoS in search

Patch available: wonderwhy-er/DesktopCommanderMCP v0.2.39 (PR #400 merged 2026-04-09)

https://github.com/wonderwhy-er/DesktopCommanderMCP/pull/400
generic🟡 PoC Available

[Security] Regular Expression Denial of Service (ReDoS) in Excel/DOCX Content Search · Issue #375 · wonderwhy-er/DesktopCommanderMCP · GitHub

https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/375
github_commit

commit 4ce845f8749b (wonderwhy-er/DesktopCommanderMCP)

Fix landed in wonderwhy-er/DesktopCommanderMCP commit 4ce845f8749b — awaiting tagged release

https://github.com/wonderwhy-er/DesktopCommanderMCP/commit/4ce845f8749b6a159b57b38dcc3357f7222a8078
generic

GitHub - wonderwhy-er/DesktopCommanderMCP: This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities · GitHub

https://github.com/wonderwhy-er/DesktopCommanderMCP/

Vendor Advisories for CVE-2026-10691(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@wonderwhy-er/desktop-commander—0.2.39—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:04 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 06:12 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-08 16:33 UTCGHSA enrichment
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 68 more
  1. 2026-07-03 20:27 UTCGHSA enrichment
  2. 2026-07-01 23:59 UTCGHSA enrichment
  3. 2026-07-01 15:06 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 22:19 UTCGHSA enrichment
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-29 11:03 UTCGHSA enrichment
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 04:46 UTCGHSA enrichment
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCGHSA enrichment
  15. 2026-06-26 01:26 UTCGHSA enrichment
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 22:26 UTCGHSA enrichment
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-23 19:23 UTCGHSA enrichment
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-20 12:57 UTCGHSA enrichment
  28. 2026-06-19 19:25 UTCEPSS rescore
  29. 2026-06-19 02:45 UTCGHSA enrichment
  30. 2026-06-18 17:52 UTCEPSS rescore
  31. 2026-06-17 23:20 UTCGHSA enrichment
  32. 2026-06-17 17:53 UTCEPSS rescore
  33. 2026-06-16 21:38 UTCGHSA enrichment
  34. 2026-06-16 17:52 UTCEPSS rescore
  35. 2026-06-15 19:58 UTCGHSA enrichment
  36. 2026-06-15 17:48 UTCEPSS rescore
  37. 2026-06-14 23:18 UTCEPSS rescore
  38. 2026-06-14 18:14 UTCGHSA enrichment
  39. 2026-06-13 23:00 UTCEPSS rescore
  40. 2026-06-13 23:00 UTCEPSS rescore
  41. 2026-06-13 16:32 UTCGHSA enrichment
  42. 2026-06-12 23:12 UTCEPSS rescore
  43. 2026-06-12 14:52 UTCGHSA enrichment
  44. 2026-06-11 14:00 UTCEPSS rescore
  45. 2026-06-11 13:11 UTCGHSA enrichment
  46. 2026-06-10 22:18 UTCEPSS rescore
  47. 2026-06-10 13:22 UTCEPSS rescore
  48. 2026-06-10 11:32 UTCGHSA enrichment
  49. 2026-06-09 09:52 UTCGHSA enrichment
  50. 2026-06-08 14:17 UTCEPSS rescore
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-08 08:13 UTCGHSA enrichment
  53. 2026-06-07 15:25 UTCEPSS rescore
  54. 2026-06-07 15:24 UTCEPSS rescore
  55. 2026-06-07 06:34 UTCGHSA enrichment
  56. 2026-06-06 13:47 UTCEPSS rescore
  57. 2026-06-06 13:47 UTCEPSS rescore
  58. 2026-06-06 13:47 UTCEPSS rescore
  59. 2026-06-06 04:54 UTCGHSA enrichment
  60. 2026-06-05 22:47 UTCEPSS rescore
  61. 2026-06-05 06:10 UTCEPSS rescore
  62. 2026-06-05 06:10 UTCEPSS rescore
  63. 2026-06-05 03:15 UTCGHSA enrichment
  64. 2026-06-04 13:12 UTCEPSS rescore
  65. 2026-06-04 13:12 UTCEPSS rescore
  66. 2026-06-04 13:12 UTCEPSS rescore
  67. 2026-06-04 01:36 UTCGHSA enrichment
  68. 2026-06-02 23:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10691?
CVE-2026-10691 is a medium vulnerability published on June 2, 2026. 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…
When was CVE-2026-10691 disclosed?
CVE-2026-10691 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10691 actively exploited?
CVE-2026-10691 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10691?
CVE-2026-10691 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-10691?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10691, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10691

Explore →

Is Your Infrastructure Affected by CVE-2026-10691?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs