Summary
Docker MCP Plugin and Docker MCP Gateway have DNS Rebinding vulnerability when running in sse or streaming mode
Workarounds
Do not start the MCP gateway in sse or streaming mode (use default stdio)
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Patch available in version v0.28.0
Frequently Asked Questions
- What is CVE-2025-64443? CVE-2025-64443 is a high-severity security vulnerability in github.com/docker/mcp-gateway (go), affecting versions <= 0.27.0. It is fixed in 0.28.0.
- Which versions of github.com/docker/mcp-gateway are affected by CVE-2025-64443? github.com/docker/mcp-gateway (go) versions <= 0.27.0 is affected.
- Is there a fix for CVE-2025-64443? Yes. CVE-2025-64443 is fixed in 0.28.0. Upgrade to this version or later.
- Is CVE-2025-64443 exploitable, and should I be worried? Whether CVE-2025-64443 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-64443 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-64443? Upgrade
github.com/docker/mcp-gatewayto 0.28.0 or later.