DNS Rebinding vulnerability present when running MCP Gateway in sse or streaming mode
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| docker | mcp-gateway | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Docker | Docker | — |
| Docker | Mcp Gateway | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-46gc-mwh4-cc5r | Docker MCP Plugin and Docker MCP Gateway have DNS Rebinding vulnerability when running in sse or streaming mode |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.456% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:docker:mcp_gateway:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Docker
Docker docker Docker mcp Gateway |
|
| Vendors & Products |
Docker
Docker docker Docker mcp Gateway |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | DNS Rebinding vulnerability present when running MCP Gateway in sse or streaming mode | |
| Weaknesses | CWE-749 | |
| References |
| |
| Metrics |
cvssV4_0
|