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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/docker/mcp-gateway/commit/6b076b2479d8d1345c50c112119c62978d46858e Patch
- https://github.com/docker/mcp-gateway/security/advisories/GHSA-46gc-mwh4-cc5r Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.3 · dockerNVD modified 2026-10-18 17:10
Affected (CPE criteria) 1
cpe:2.3:a:docker:mcp_gateway:*:*:*:*:*:*:*:*