CVE-2026-116102 QuantGeekDev docker-mcp docker_executor.py _build_windows_command os command injection
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-116102 and fix it if it is affected.
What it is: CVE-2026-116102 is a medium-severity vulnerability in QuantGeekDev docker-mcp, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-116102 in the wild and no public exploit code.
Affected product: QuantGeekDev docker-mcp. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-116102/ (Markdown: https://insights.sbomify.com/CVE-2026-116102/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116102?
CVE-2026-116102 is a medium-severity vulnerability in QuantGeekDev docker-mcp, published on 26 Oct 2026.
Official description
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.
Which versions are affected by CVE-2026-116102?
How do I fix CVE-2026-116102?
No fix has been published for CVE-2026-116102 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116102 being exploited?
There is no known exploitation of CVE-2026-116102 in the wild and no public exploit code.
Sources
Also known as GHSA-7mj2-6mxg-wcx9.