Description

A vulnerability has been found in MissionSquad mcp-api up to 1.11.8. The impacted element is the function this.packageService.installPackage of the file src/controllers/packages.ts of the component NPM Package Version Handler. The manipulation leads to command injection. It is possible to initiate the attack remotely. Upgrading to version 1.11.9 is sufficient to resolve this issue. The identifier of the patch is a40f54d4533ba6618e1749383a245900eeb024c1. The affected component should be upgraded.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.3",
  "pubDate": "2026-08-06T14:16:36.223Z",
  "pubdate": "2026-08-06T14:16:36.223Z",
  "executiveSummary": "A critical command injection vulnerability has been identified in the MissionSquad mcp-api component, specifically within the NPM Package Version Handler. The flaw resides in the function this.packageService.installPackage located within src/controllers/packages.ts. This vulnerability allows remote attackers to execute arbitrary system commands on the underlying host operating system by manipulating input processed by the package installation service. Successful exploitation can lead to total system compromise, unauthorized access to sensitive data, and potential lateral movement within the network infrastructure. The attack vector is fully remote, requiring no pre-existing authentication or elevated privileges if the vulnerable endpoint is exposed to the network. Organizations utilizing affected versions of the software face severe confidentiality, integrity, and availability risks. Mitigation requires an immediate upgrade to version 1.11.9, which applies the necessary vendor patch identified by commit hash a40f54d4533ba6618e1749383a245900eeb024c1.",
  "technicalDetails": "The vulnerability stems from insufficient validation and sanitization of user-supplied data passed to the package installation mechanism within the NPM Package Version Handler component of MissionSquad mcp-api up to version 1.11.8. Specifically, the execution flow involves the function this.packageService.installPackage inside the source file src/controllers/packages.ts. When untrusted input representing package versions or identifiers is processed by this function, it is improperly concatenated or passed directly into a low-level system shell execution context without adequate neutralization of shell metacharacters.\nThe exploitation method relies on injecting malicious command separators or payload sequences (such as semicolons, pipes, or backticks) into the parameters accepted by the vulnerable API endpoint. Because the attack can be initiated remotely, an unauthenticated or remotely positioned threat actor can transmit a crafted HTTP request containing the malicious payload directly to the application interface. Upon receipt, the application forwards the unsanitized input to the operating system shell via the package installation routine, triggering the execution of the injected commands with the privileges of the running Node.js process.\nThe attack flow proceeds as follows: First, the adversary identifies the exposed API endpoint associated with the NPM Package Version Handler. Second, the attacker constructs a payload designed to break out of the intended package installation command arguments and execute arbitrary system binaries. Third, the crafted request is sent over the network to the server hosting mcp-api. Fourth, the src/controllers/packages.ts file processes the request, and the this.packageService.installPackage function passes the unsanitized payload to the underlying execution sink. Finally, the operating system executes the injected commands, resulting in complete remote code execution and subsequent post-exploitation behaviors such as reverse shell establishment, data exfiltration, or persistence mechanisms."
}