<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 19 Oct 2026 13:39:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252220</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252220</link>
      <description>EUVD-2026-252220</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252220</guid>
    </item>
    <item>
      <title>fkie_cve-2025-54994</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-54994</link>
      <description>&lt;p&gt;@akoskm/create-mcp-server-stdio is an MCP server starter kit that uses the StdioServerTransport. Prior to version 0.0.13, the MCP Server is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server exposes the tool `which-app-on-port` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input. Version 0.0.13 contains a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@akoskm/create-mcp-server-stdio is an MCP server starter kit that uses the StdioServerTransport. Prior to version 0.0.13, the MCP Server is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server exposes the tool `which-app-on-port` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input. Version 0.0.13 contains a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-54994</guid>
    </item>
    <item>
      <title>GHSA-3ch2-jxxc-v4xf — @akoskm/create-mcp-server-stdio is vulnerable to MCP Server Command Injection through `exec` API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3ch2-jxxc-v4xf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @akoskm/create-mcp-server-stdio&lt;/p&gt;
&lt;p&gt;# Command Injection in MCP Server&lt;/p&gt;
&lt;p&gt;The MCP Server at https://github.com/akoskm/create-mcp-server-stdio is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation.&lt;/p&gt;
&lt;p&gt;## Vulnerable tool&lt;/p&gt;
&lt;p&gt;The MCP Server exposes the tool `which-app-on-port` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input.&lt;/p&gt;
&lt;p&gt;Vulnerable line of code: https://github.com/akoskm/create-mcp-server-stdio/blob/main/src/index.ts#L24-L40&lt;/p&gt;
&lt;p&gt;```js
server.tool(&amp;#34;which-app-on-port&amp;#34;, { port: z.number() }, async ({ port }) =&amp;gt; {
  const result = await new Promise&amp;lt;ProcessInfo&amp;gt;((resolve, reject) =&amp;gt; {
    exec(`lsof -t -i tcp:${port}`, (error, pidStdout) =&amp;gt; {
      if (error) {
        reject(error);
        return;
      }
      const pid = pidStdout.trim();
      exec(`ps -p ${pid} -o comm=`, (error, stdout) =&amp;gt; {
        if (error) {
          reject(error);
          return;
        }
        resolve({ command: stdout.trim(), pid });
      });
    });
  });
```&lt;/p&gt;
&lt;p&gt;## Exploitation&lt;/p&gt;
&lt;p&gt;When LLMs are tricked through prompt injection (and other techniques and attack vectors) to call the tool with input that uses special shell characters such as `; rm -rf /tmp;#` (be careful actually executing this payload) and other payload variations, the full command-line text will be interepted by the shell and result in other commands except of `ps` executing on the host running the M…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @akoskm/create-mcp-server-stdio&lt;/p&gt;
&lt;p&gt;# Command Injection in MCP Server&lt;/p&gt;
&lt;p&gt;The MCP Server at https://github.com/akoskm/create-mcp-server-stdio is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation.&lt;/p&gt;
&lt;p&gt;## Vulnerable tool&lt;/p&gt;
&lt;p&gt;The MCP Server exposes the tool `which-app-on-port` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input.&lt;/p&gt;
&lt;p&gt;Vulnerable line of code: https://github.com/akoskm/create-mcp-server-stdio/blob/main/src/index.ts#L24-L40&lt;/p&gt;
&lt;p&gt;```js
server.tool(&amp;#34;which-app-on-port&amp;#34;, { port: z.number() }, async ({ port }) =&amp;gt; {
  const result = await new Promise&amp;lt;ProcessInfo&amp;gt;((resolve, reject) =&amp;gt; {
    exec(`lsof -t -i tcp:${port}`, (error, pidStdout) =&amp;gt; {
      if (error) {
        reject(error);
        return;
      }
      const pid = pidStdout.trim();
      exec(`ps -p ${pid} -o comm=`, (error, stdout) =&amp;gt; {
        if (error) {
          reject(error);
          return;
        }
        resolve({ command: stdout.trim(), pid });
      });
    });
  });
```&lt;/p&gt;
&lt;p&gt;## Exploitation&lt;/p&gt;
&lt;p&gt;When LLMs are tricked through prompt injection (and other techniques and attack vectors) to call the tool with input that uses special shell characters such as `; rm -rf /tmp;#` (be careful actually executing this payload) and other payload variations, the full command-line text will be interepted by the shell and result in other commands except of `ps` executing on the host running the M…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3ch2-jxxc-v4xf</guid>
    </item>
  </channel>
</rss>
