@akoskm/create-mcp-server-stdio is vulnerable to MCP Server Command Injection through `exec` API
CVE-2025-54994 · GHSA-3ch2-jxxc-v4xf · published 2025-09-08 · updated 2025-09-10
- Severity
- Critical
- CVSS score
- 9.3
- Chance of exploitation (EPSS)
- 1.3%
- Fixed in
- 0.0.13
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
User initiated and remote command injection on a running MCP Server.
Upgrade @akoskm/create-mcp-server-stdio to 0.0.13 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Don't use exec. Use execFile instead, which pins the command and provides the arguments as array elements. If the user input is not a command-line flag, use the -- notation to terminate command and command-line flag, and indicate that the text after the -- double dash notation is benign value.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @akoskm/create-mcp-server-stdio | npm | < 0.0.13 | 0.0.13 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.