Is CVE-2026-10691 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10691 being exploited in the wild.

How severe is CVE-2026-10691?

Medium severity, with a CVSS score of 4.3, published 3 June 2026.

Which products and versions are affected?

@wonderwhy-er/desktop-commander (npm) < 0.2.39, SEMVER:introduced=0,fixed=0.2.39; Wonderwhy-Er DesktopCommanderMCP < 0.2.39, up to 0.2.38.

Is there a fix for CVE-2026-10691?

Yes. @wonderwhy-er/desktop-commander (npm): upgrade to 0.2.39 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-10691 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-10691?

Check whether you run @wonderwhy-er/desktop-commander (npm) or Wonderwhy-Er DesktopCommanderMCP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10691: wonderwhy-er DesktopCommanderMCP ReDoS in search-manager

Q: Is there a fix for CVE-2026-10691?

Yes. @wonderwhy-er/desktop-commander (npm): upgrade to 0.2.39 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-10691 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-10691?

Check whether you run @wonderwhy-er/desktop-commander (npm) or Wonderwhy-Er DesktopCommanderMCP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10691 · Severity: medium · CVSS 4.3 · Published 2026-06-03

DesktopCommanderMCP, a tool used to provide AI assistants with file system and terminal access, is vulnerable to a denial-of-service attack. By providing a specially crafted search pattern, an attacker can cause the application to consume 100% of the CPU, making the AI assistant unresponsive. This can be triggered remotely through prompt injection or by manipulating the search parameters used by the AI agent.

Technologies: Wonderwhy-Er DesktopCommanderMCP. Vendors: npm, Wonderwhy-Er.

Quick answers

Is CVE-2026-10691 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10691 being exploited in the wild.
How severe is CVE-2026-10691?: Medium severity, with a CVSS score of 4.3, published 3 June 2026.
Which products and versions are affected?: @wonderwhy-er/desktop-commander (npm) < 0.2.39, SEMVER:introduced=0,fixed=0.2.39; Wonderwhy-Er DesktopCommanderMCP < 0.2.39, up to 0.2.38.
Is there a fix for CVE-2026-10691?: Yes. @wonderwhy-er/desktop-commander (npm): upgrade to 0.2.39 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-10691 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-10691?: Check whether you run @wonderwhy-er/desktop-commander (npm) or Wonderwhy-Er DesktopCommanderMCP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@wonderwhy-er/desktop-commander (npm): upgrade to 0.2.39 or later
```
npm install @wonderwhy-er/desktop-commander@0.2.39
```

Technical details

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the `start_search` tool of DesktopCommanderMCP within `src/search-manager.ts`. The application uses the native JavaScript `RegExp` engine to process user-supplied search patterns when scanning Excel (.xlsx) and DOCX (.docx) files. Because these patterns are compiled and executed without complexity limits or timeouts, an attacker can provide a pattern designed to trigger catastrophic backtracking (e.g., `(a+)+$`). This blocks the Node.js event loop, leading to uncontrolled resource consumption and a complete hang of the MCP server. The vulnerability can be exploited remotely, for example, via prompt injection against an AI agent that has access to the tool. The issue is fixed in version 0.2.39 by implementing safer regex handling.

Affected products

wonderwhy-er DesktopCommanderMCP < 0.2.39

Identifiers

CVE-2026-10691
GHSA-r87g-78mx-3wg4

Timeline

2026-06-03: disclosed
2026-06-03: advisory
2026-07-10: patched: GitHub advisory updated with patch details

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.