All vulnerabilities
CVE-2026-55157GHSA-49mq-fc6q-3h46

token-optimizer-mcp: Token Optimizer MCP: OS command injection in smart_user via username in get-user-info

ooples token-optimizer-mcpnpmLibraries & packages
Open in ThreatlineRecord JSON
CVSS
8.4High
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 1 Oct 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.70%Chance of exploitation activity in the next 30 days, higher than 52% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in5.1.0Fixed versionOSV
Published28 Sep 2026Updated 1 Oct 2026CVE List

What fixes it

  • 5.1.0@ooples/token-optimizer-mcp, npmOSVnpm install @ooples/token-optimizer-mcp@5.1.0

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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.

Text from CVE List

Affected versions 2

  • token-optimizer-mcpaffected: < 5.1.0CVE List
  • @ooples/token-optimizer-mcp, npmfrom first release, fixed in 5.1.0OSV

References 3