Docker MCP Plugin and Docker MCP Gateway have DNS Rebinding vulnerability when running in sse or streaming mode

緊急 9.6CVE-2025-64443 · GHSA-46gc-mwh4-cc5r · GO-2025-4179 · 03/12/2025 公開 · 18/10/2026 更新

要点

CVE-2025-64443 は github.com/docker/mcp-gateway, mcp gateway (docker) に影響する深刻度「緊急」 (CVSS 9.6) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.43%（全脆弱性の 36.8% より高い）。
対処：0.28.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
github.com/docker/mcp-gateway Go	`< 0.28.0`	`0.28.0`
mcp gateway docker	`< 0.28.0`	`0.28.0`

概要

Impact

When ran in sse or streaming mode (--transport), the Docker MCP Gateway is vulnerable to a DNS rebinding attack.

Vulnerability allows for Browser-Based exploitation of any MCP servers that are executing within the Docker MCP Gateway. Any tools or other features exposed by MCP servers can be manipulated by an attacker who is able to get a victim to visit a malicious website, or if a victim is served a malicious advertisement.

The MCP Gateway is not prone to this attack when started in its default stdio mode, which does not listen on any network ports.

Patches

Patch available in version v0.28.0

Workarounds

Do not start the MCP gateway in sse or streaming mode (use default stdio)

NVD の説明

MCP Gateway allows easy and secure running and deployment of MCP servers. In versions 0.27.0 and earlier, when MCP Gateway runs in sse or streaming transport mode, it is vulnerable to DNS rebinding. An attacker who can get a victim to visit a malicious website or be served a malicious advertisement can perform browser-based exploitation of MCP servers executing behind the gateway, including manipulating tools or other features exposed by those MCP servers. MCP Gateway is not affected when running in the default stdio mode, which does not listen on network ports. Version 0.28.0 fixes this issue.