Live › vulnerability › CVE-2026-116102
Go to dashboardThe docker-mcp MCP server builds a Windows command in _build_windows_command from the project_name argument without sanitizing it. A remote attacker who controls that argument can inject operating system commands that run on the host.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 01:38 UTC. All times on this page are UTC.
Teams that run the docker-mcp server from QuantGeekDev, versions 0.1.0 and 0.2.0, on Windows where the project_name argument can be supplied by a remote caller. Installations that do not run the server, or that run it only with trusted local input, are less exposed. The sources do not say which deployment modes are reachable from the internet.
No product ranges from the sources yet.
pip show docker-mcp or inspect the package lockfile for docker-mcp at 0.1.0 or 0.2.0_build_windows_command in docker_executor.pydocker-mcp 0.1.0 and 0.2.0 to a fixed release; unknown which version fixes itEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability was determined in QuantGeekDev docker-mcp 0.1.0/0.2.0. The impacted element is the function _build_windows_command of the file docker_executor.py. This manipulation of the argument project_name causes os command injection. It is possible to initiate the attack remotely.
This page as .md · .json · in your agent: get_signal("CVE-2026-116102")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.