Docker Mcp
Monthly
OS command injection in QuantGeekDev docker-mcp 0.1.0 and 0.2.0 allows an attacker who can influence the project_name argument to inject arbitrary shell commands through the Windows-specific command builder in docker_executor.py. The vulnerable path is exercised only on Windows deployments, and the CVSS UI:P component means a user or agent must invoke the affected MCP tool before the payload is assembled, so it does not fire passively. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor's CVSS 4.0 base score is 5.3, while our independent assessment rates it higher (7.5-equivalent impact under CVSS 3.1) because successful injection yields full command execution.
OS command injection in QuantGeekDev docker-mcp 0.1.0 and 0.2.0 allows an attacker who can influence the project_name argument to inject arbitrary shell commands through the Windows-specific command builder in docker_executor.py. The vulnerable path is exercised only on Windows deployments, and the CVSS UI:P component means a user or agent must invoke the affected MCP tool before the payload is assembled, so it does not fire passively. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor's CVSS 4.0 base score is 5.3, while our independent assessment rates it higher (7.5-equivalent impact under CVSS 3.1) because successful injection yields full command execution.