Skip to main content
CVE-2025-53372VulnerabilityPublished

CVE-2025-53372: alfonsograziano node-code-sandbox-mcp · Command Injection

Affects alfonsograziano node-code-sandbox-mcpSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3.0 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade alfonsograziano node-code-sandbox-mcp to 1.3.0.

Affected software

ProductAffectedFixed in
npmnode-code-sandbox-mcppkg:npm/node-code-sandbox-mcpOther threatsAffected
  • <1.3.0
Fixed in
  • 1.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to node-code-sandbox-mcp version 1.3.0 or later, where the vulnerability is patched. 2. Implement strict input validation and sanitization on all user-supplied parameters before they are passed to system command execution functions. Use safe APIs that avoid shell interpretation, such as child_process.execFile or spawn with argument arrays, instead of execSync with concatenated strings. 3. Employ runtime application self-protection (RASP) or behavior monitoring to detect and block suspicious command execution patterns. 4. Restrict the privileges of the node-code-sandbox-mcp server process to the minimum necessary, using container security best practices and Linux capabilities to limit potential damage from exploitation. 5. Use container security tools to enforce strict isolation policies and monitor container escape attempts. 6. Conduct regular security audits and code reviews focusing on command injection risks in all components that execute system commands. 7. Educate users and administrators about the risk of social engineering attacks that could trigger this vulnerability, emphasizing cautious handling of untrusted inputs. 8. Deploy network-level protections such as Web Application Firewalls (WAFs) with custom rules to detect and block command injection payloads targeting this service. 9. Monitor logs for unusual command execution or container behavior indicative of exploitation attempts.

Description

node-code-sandbox-mcp is a Node.js–based Model Context Protocol server that spins up disposable Docker containers to execute arbitrary JavaScript. Prior to 1.3.0, a command injection vulnerability exists in the node-code-sandbox-mcp MCP Server. The vulnerability is caused by the unsanitized use of input parameters within a call to child_process.execSync, enabling an attacker to inject arbitrary system commands. Successful exploitation can lead to remote code execution under the server process's privileges on the host machine, bypassing the sandbox protection of running code inside docker. This vulnerability is fixed in 1.3.0.

References

Community reviews

Loading reviews…