EUVD-2026-54766
GHSA-c8c4-xf97-vvc8
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
AV:N and PR:N confirmed by CVSS 4.0 vector; C/I/A elevated to High because command injection in a command-dispatching endpoint typically yields arbitrary OS code execution, contradicting the provided Low impact ratings which are unsubstantiated.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
1DescriptionCVE.org
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.
AnalysisAI
Command injection in INQUIRELAB mcp-bridge-api's Servers Endpoint allows unauthenticated remote attackers to execute arbitrary OS commands by manipulating the command/args parameters in mcp-bridge.js without sanitization. The product uses a rolling release model and all commits up to b30a82aa1d1d1139e0de846c41c8aadee6e06114 are confirmed affected. No released patch exists - a remediation pull request has been submitted but was awaiting acceptance at time of disclosure. No public exploit or KEV listing identified at time of analysis.
Technical ContextAI
mcp-bridge-api (CPE: cpe:2.3:a:inquirelab:mcp-bridge-api:*:*:*:*:*:*:*:*) is a Node.js bridge implementation for the Model Context Protocol (MCP), designed to proxy or relay requests to backend MCP servers. The Servers Endpoint in mcp-bridge.js passes user-controlled command and args parameters directly to a shell execution call without neutralizing shell metacharacters or special elements. CWE-77 (Improper Neutralization of Special Elements used in a Command) identifies this root cause class: the application constructs a system command using externally-supplied input without correctly stripping or escaping characters such as semicolons, pipes, backticks, or ampersands that alter the intended command structure. Because MCP bridge APIs are architecturally designed to dispatch commands to server processes, the attack surface is directly exposed at a functional endpoint rather than an incidental one.
RemediationAI
No vendor-released patched version exists at time of analysis - a pull request to address the issue has been submitted but awaits acceptance (see https://github.com/INQUIRELAB/mcp-bridge-api/issues/1 and https://github.com/INQUIRELAB/mcp-bridge-api/issues/1#issuecomment-4320749148). Operators should monitor the repository at https://github.com/INQUIRELAB/mcp-bridge-api/ for merge of the remediation PR and deploy the updated commit immediately upon release. In the interim, the most effective compensating control is to restrict network access to the Servers Endpoint using a firewall or reverse proxy, limiting connectivity to trusted internal hosts only - this directly counters the AV:N attack vector but requires maintaining an allowlist of legitimate callers. If the Servers Endpoint is not required, disable or remove it from the running configuration to eliminate the attack surface entirely. Input validation via an API gateway that rejects command/args values containing shell metacharacters (semicolons, pipes, backticks, dollar signs, ampersands) can reduce exploitation probability but is not a reliable substitute for source-level sanitization and may block legitimate requests depending on expected argument formats.
Same weakness CWE-77 – Command Injection
View allSame technique Command Injection
View allShare
External POC / Exploit Code
Leaving vuln.today