CVE-2026-19263
Received Received - Intake

Command Injection in INQUIRELAB mcp-bridge-api

Publication date: 2026-08-08

Last updated on: 2026-08-08

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-08
Last Modified
2026-08-08
Generated
2026-08-08
AI Q&A
2026-08-08
EPSS Evaluated
N/A
NVD
CVE-2026-19263
EUVD
EUVD-2026-54766

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
inquirelab mcp-bridge-api to b30a82aa1d1d1139e0de846c41c8aadee6e06114 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-77 The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a command injection flaw in INQUIRELAB mcp-bridge-api. It allows unauthenticated remote attackers to execute arbitrary commands on the server hosting the bridge service by manipulating the command/args input in the POST /servers endpoint. The issue arises because user-controlled inputs are passed directly to the startServer function, which uses spawn to launch processes without proper restrictions.

Detection Guidance

To detect this vulnerability, monitor network traffic for unauthorized POST requests to the /servers endpoint in INQUIRELAB mcp-bridge-api. Check server logs for suspicious command execution patterns or unexpected process spawns. Use tools like netstat or ss to identify active connections to the bridge service. Inspect the mcp-bridge.js file for direct use of spawn functions without input validation.

Impact Analysis

An attacker could exploit this to run malicious commands on your server with the same privileges as the bridge service. This could lead to unauthorized data access, system compromise, or further network infiltration. The impact depends on the service's permissions but may include data theft, service disruption, or full system takeover.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and security controls. GDPR requires adequate technical measures to prevent unauthorized access, while HIPAA mandates strict access controls and audit mechanisms. Exploitation could lead to data breaches, triggering mandatory breach notifications and potential fines.

Mitigation Strategies

Immediately restrict access to the POST /servers endpoint by implementing strict authentication and authorization. Disable or remove the endpoint if not required. Use allowlists to restrict executable paths and command arguments. Replace shell-assisted spawning with safer alternatives like child_process.execFile. Monitor for any signs of exploitation and update the bridge service once a patch is available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19263. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart