Description

A vulnerability was found in INQUIRELAB mcp-bridge-api up to b30a82aa1d1d1139e0de846c41c8aadee6e06114. The impacted element is an unknown function of the file mcp-bridge.js of the component Servers Endpoint. Performing a manipulation of the argument command/args results in command injection. It is possible to initiate the attack remotely. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The pull request to fix this issue awaits acceptance.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-08-08T07:17:11.790Z",
  "pubdate": "2026-08-08T07:17:11.790Z",
  "executiveSummary": "A command injection vulnerability has been identified in the INQUIRELAB mcp-bridge-api project, specifically within the mcp-bridge.js file of the Servers Endpoint component, affecting commits up to b30a82aa1d1d1139e0de846c41c8aadee6e06114. This critical security flaw allows remote attackers to execute arbitrary system commands on the underlying host by manipulating the command or args arguments. Because the application utilizes a rolling release model, traditional version numbering is unavailable, and users must rely on commit hashes to track exposure. The presence of this vulnerability poses severe risk implications, including potential remote code execution, unauthorized system access, data exfiltration, and complete compromise of the host environment. Successful exploitation requires network accessibility to the vulnerable endpoint and does not explicitly require prior authentication based on the provided data, enabling remote threat actors to trigger the flaw directly.",
  "technicalDetails": "The vulnerability resides in the mcp-bridge.js file associated with the Servers Endpoint component of the INQUIRELAB mcp-bridge-api. The root cause stems from insecure handling and insufficient sanitization of user-supplied input passed via the command and args parameters. When the application processes these arguments without proper validation or parameterization, the input is improperly concatenated or passed directly into a low-level operating system shell execution sink (such as child_process.exec or similar constructs in Node.js).\nAn attacker can exploit this flaw remotely by crafting malicious HTTP requests or payload structures sent to the Servers Endpoint. By injecting shell metacharacters, command separators, or arbitrary executable strings into the command or args parameters, the attacker can break out of the intended argument context and execute arbitrary system commands with the privileges of the running Node.js process. The attack flow begins with the remote attacker identifying the exposed Servers Endpoint, formulating an input string containing malicious shell commands, and transmitting the payload to the vulnerable mcp-bridge.js component. Upon ingestion, the application executes the tainted string directly via the underlying operating system shell, thereby achieving command injection.\nThe impacted element involves an unknown function within mcp-bridge.js that processes execution requests up to commit b30a82aa1d1d1139e0de846c41c8aadee6e06114. Network exposure is present due to the remote accessibility of the Servers Endpoint. Depending on the operational context of the deployment, the process may run with elevated privileges, amplifying the post-exploitation impact. The pull request to address this issue is currently awaiting acceptance, meaning unmitigated instances remain vulnerable until the fix is officially merged and deployed."
}