CVE-2026-116102: A vulnerability was determined in QuantGeekDev docker-mcp 0.1.0/0.2.0
CVE-2026-116102 is a medium-severity flaw (CVSS 6.3) affecting docker-mcp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- On your watchlist
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-116102?
docker-mcp: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-116102 being exploited?
CVE-2026-116102 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-116102 affect?
CVE-2026-116102 affects docker-mcp. Severity is medium (CVSS 6.3). 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. I
How urgent is CVE-2026-116102?
Priority 27/100. On your watchlist
Software pages
Docker vulnerabilities · Windows vulnerabilities