Quick answers
- Is CVE-2026-6942 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6942 being exploited in the wild.
- How severe is CVE-2026-6942?
- Critical severity, with a CVSS score of 9.8, published 23 April 2026.
- Which products and versions are affected?
- Radareorg Radare2-Mcp <= 1.6.0.
- Is there a fix for CVE-2026-6942?
- A patch was published on 2026-04-23: Fix committed to radare2-mcp repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6942 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6942?
- Check whether you run Radare2 Mcp Server or Radareorg Radare2-Mcp 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.
Technical details
An OS command injection vulnerability exists in radare2-mcp versions 1.6.0 and earlier due to improper neutralization of shell metacharacters in user-controlled input. The vulnerability is reachable via the JSON-RPC interface, specifically through the 'run_javascript' and 'run_command' tools which pass input to the 'r2_cmd_str()' function. Attackers can use the radare2 shell escape character ('!') to bypass command filters and achieve remote code execution (RCE) on the host machine. This can be exploited directly via the network or indirectly through prompt injection if an LLM agent is used to analyze a malicious binary. The issue is fixed in version 1.7.0 by enabling sandbox mode by default.
Affected products
- radareorg radare2-mcp <= 1.6.0
Timeline
- 2026-03-23: disclosed: Issue reported on GitHub by researcher Manthan Ghasadiya
- 2026-04-23: advisory: NVD and VulnCheck published advisory
- 2026-04-23: patched: Fix committed to radare2-mcp repository