<?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://db.gcve.eu</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>Thu, 08 Oct 2026 18:33:12 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55157</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-55157</link>
      <description>&lt;p&gt;Token Optimizer MCP measures token savings per AI coding agent, optimizes context, and shares a live local knowledge graph across 16 CLI clients. Prior to version 5.1.0, token-optimizer-mcp is vulnerable to OS command injection in the smart_user tool. Any MCP client that can call the smart_user tool can execute arbitrary shell commands through the username argument of the get-user-info operation. The commands execute with the privileges of the user running the token-optimizer-mcp server. This issue has been patched in version 5.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Token Optimizer MCP measures token savings per AI coding agent, optimizes context, and shares a live local knowledge graph across 16 CLI clients. Prior to version 5.1.0, token-optimizer-mcp is vulnerable to OS command injection in the smart_user tool. Any MCP client that can call the smart_user tool can execute arbitrary shell commands through the username argument of the get-user-info operation. The commands execute with the privileges of the user running the token-optimizer-mcp server. This issue has been patched in version 5.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-55157</guid>
    </item>
    <item>
      <title>GHSA-49mq-fc6q-3h46 — Token Optimizer MCP: OS command injection in smart_user via username in get-user-info</title>
      <link>https://db.gcve.eu/vuln/ghsa-49mq-fc6q-3h46</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @ooples/token-optimizer-mcp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`token-optimizer-mcp` is vulnerable to OS command injection in the `smart_user` tool.&lt;/p&gt;
&lt;p&gt;The `get-user-info` operation accepts a user-controlled `username` argument and later interpolates it into a shell command executed through `execAsync()`:&lt;/p&gt;
&lt;p&gt;```ts
getent passwd &amp;#34;${username}&amp;#34; || grep &amp;#34;^${username}:&amp;#34; /etc/passwd
```&lt;/p&gt;
&lt;p&gt;Although the value is wrapped in double quotes, POSIX shells still evaluate command substitution such as `$(...)` and backticks inside double quotes. As a result, an MCP client can provide a crafted username such as:&lt;/p&gt;
&lt;p&gt;```text
$(id &amp;gt; /tmp/TOKEN_OPTIMIZER_SMART_USER_ID)
```&lt;/p&gt;
&lt;p&gt;and execute arbitrary local commands with the privileges of the user running the MCP server.&lt;/p&gt;
&lt;p&gt;This is a CWE-78 OS command injection issue.&lt;/p&gt;
&lt;p&gt;Tested version:&lt;/p&gt;
&lt;p&gt;```text
@ooples/token-optimizer-mcp v5.0.1
MCP serverInfo.name: token-optimizer-mcp
MCP serverInfo.version: 0.2.0
```&lt;/p&gt;
&lt;p&gt;This issue is not related to the current `npm audit` dependency advisories. The vulnerability is in `token-optimizer-mcp`&amp;#39;s own tool implementation.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerable code path is in the `smart_user` implementation.&lt;/p&gt;
&lt;p&gt;The `username` argument is eventually passed into a shell command similar to:&lt;/p&gt;
&lt;p&gt;```ts
const { stdout: passwdOut } = await execAsync(
  `getent passwd &amp;#34;${username}&amp;#34; || grep &amp;#34;^${username}:&amp;#34; /etc/passwd`
);
```&lt;/p&gt;
&lt;p&gt;The problem is that `username` is controlled by the MCP tool caller and is inserted into a command string executed by a shell.&lt;/p&gt;
&lt;p&gt;Double quotes do not make this safe. In POSIX she…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @ooples/token-optimizer-mcp&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`token-optimizer-mcp` is vulnerable to OS command injection in the `smart_user` tool.&lt;/p&gt;
&lt;p&gt;The `get-user-info` operation accepts a user-controlled `username` argument and later interpolates it into a shell command executed through `execAsync()`:&lt;/p&gt;
&lt;p&gt;```ts
getent passwd &amp;#34;${username}&amp;#34; || grep &amp;#34;^${username}:&amp;#34; /etc/passwd
```&lt;/p&gt;
&lt;p&gt;Although the value is wrapped in double quotes, POSIX shells still evaluate command substitution such as `$(...)` and backticks inside double quotes. As a result, an MCP client can provide a crafted username such as:&lt;/p&gt;
&lt;p&gt;```text
$(id &amp;gt; /tmp/TOKEN_OPTIMIZER_SMART_USER_ID)
```&lt;/p&gt;
&lt;p&gt;and execute arbitrary local commands with the privileges of the user running the MCP server.&lt;/p&gt;
&lt;p&gt;This is a CWE-78 OS command injection issue.&lt;/p&gt;
&lt;p&gt;Tested version:&lt;/p&gt;
&lt;p&gt;```text
@ooples/token-optimizer-mcp v5.0.1
MCP serverInfo.name: token-optimizer-mcp
MCP serverInfo.version: 0.2.0
```&lt;/p&gt;
&lt;p&gt;This issue is not related to the current `npm audit` dependency advisories. The vulnerability is in `token-optimizer-mcp`&amp;#39;s own tool implementation.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerable code path is in the `smart_user` implementation.&lt;/p&gt;
&lt;p&gt;The `username` argument is eventually passed into a shell command similar to:&lt;/p&gt;
&lt;p&gt;```ts
const { stdout: passwdOut } = await execAsync(
  `getent passwd &amp;#34;${username}&amp;#34; || grep &amp;#34;^${username}:&amp;#34; /etc/passwd`
);
```&lt;/p&gt;
&lt;p&gt;The problem is that `username` is controlled by the MCP tool caller and is inserted into a command string executed by a shell.&lt;/p&gt;
&lt;p&gt;Double quotes do not make this safe. In POSIX she…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-49mq-fc6q-3h46</guid>
    </item>
  </channel>
</rss>
