https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 22:43:25 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-02007 bdu:2026-02007 https://cve.radiocsirt.org/vuln/bdu:2026-02007 https://cve.radiocsirt.org/vuln/euvd-2026-246701 EUVD-2026-246701 https://cve.radiocsirt.org/vuln/euvd-2026-246701 https://cve.radiocsirt.org/vuln/fkie_cve-2025-53372 <p>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&#39;s privileges on the host machine, bypassing the sandbox protection of running code inside docker. This vulnerability is fixed in 1.3.0.</p> <p>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&#39;s privileges on the host machine, bypassing the sandbox protection of running code inside docker. This vulnerability is fixed in 1.3.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-53372 https://cve.radiocsirt.org/vuln/ghsa-5w57-2ccq-8w95 <p><strong>Affected:</strong> npm: node-code-sandbox-mcp</p> <p>### Summary</p> <p>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&#39;s privileges on the host machine, bypassing the sandbox protection of running code inside docker.</p> <p>The server constructs and executes shell commands using unvalidated user input directly within command-line strings. This introduces the possibility of shell metacharacter injection (`|`, `&gt;`, `&amp;&amp;`, etc.).</p> <p>### Details</p> <p>The MCP Server exposes tools to run code inside a docker container. An MCP Client can be instructed to execute additional actions for example via indirect prompt injection when asked to generate code that read a file. Below some example of vulnerable code and different ways to test this vulnerability including a real example of indirect prompt injection that can lead to arbitrary command injection (bypassing sandboxing).</p> <p>### Vulnerable code</p> <p>The following snippet illustrates the vulnerable code pattern used in the MCP Server’s tooling. **Note**: These is only one instance, but similar patterns may exist elsewhere in the codebase. ```js // https://github.com/alfonsograziano/node-code-sandbox-mcp/blob/v1.2.0/src/tools/stop.ts#L22 import { execSync } from &#39;node:child_process&#39;; ...</p> <p>export default async function stopSa…</p> <p><strong>Affected:</strong> npm: node-code-sandbox-mcp</p> <p>### Summary</p> <p>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&#39;s privileges on the host machine, bypassing the sandbox protection of running code inside docker.</p> <p>The server constructs and executes shell commands using unvalidated user input directly within command-line strings. This introduces the possibility of shell metacharacter injection (`|`, `&gt;`, `&amp;&amp;`, etc.).</p> <p>### Details</p> <p>The MCP Server exposes tools to run code inside a docker container. An MCP Client can be instructed to execute additional actions for example via indirect prompt injection when asked to generate code that read a file. Below some example of vulnerable code and different ways to test this vulnerability including a real example of indirect prompt injection that can lead to arbitrary command injection (bypassing sandboxing).</p> <p>### Vulnerable code</p> <p>The following snippet illustrates the vulnerable code pattern used in the MCP Server’s tooling. **Note**: These is only one instance, but similar patterns may exist elsewhere in the codebase. ```js // https://github.com/alfonsograziano/node-code-sandbox-mcp/blob/v1.2.0/src/tools/stop.ts#L22 import { execSync } from &#39;node:child_process&#39;; ...</p> <p>export default async function stopSa…</p> https://cve.radiocsirt.org/vuln/ghsa-5w57-2ccq-8w95