# CVE-2025-64443: DNS Rebinding vulnerability present when running MCP Gateway in sse or streaming mode

> Attacker can exploit DNS rebinding in SSE or streaming modes to manipulate MCP servers behind the gateway.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Dec 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-46gc-mwh4-cc5r, GO-2025-4179

## What is CVE-2025-64443?

CVE-2025-64443 is a high-severity server-side request forgery vulnerability in docker mcp-gateway, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

## Which versions are affected by CVE-2025-64443?

3 open source packages ship an affected version, including github.com/docker/mcp-gateway. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/docker/mcp-gateway` | Go | All versions | 0.28.0 |
| `github.com/docker/mcp-gateway` | Go | All versions | 0.28.0 |
| `github.com/docker/mcp-gateway` | Go | All versions | 0.28.0 |

Products: Docker Mcp Gateway.

## How do I fix CVE-2025-64443?

Upgrade github.com/docker/mcp-gateway to 0.28.0 or later.

## Is CVE-2025-64443 being exploited?

There is no known exploitation of CVE-2025-64443 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64443 and fix it if it is affected.

What it is: CVE-2025-64443 is a high-severity server-side request forgery vulnerability in docker mcp-gateway, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-64443 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/docker/mcp-gateway (Go): affected all versions; fixed in 0.28.0
- github.com/docker/mcp-gateway (Go): affected all versions; fixed in 0.28.0
- github.com/docker/mcp-gateway (Go): affected all versions; fixed in 0.28.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64443/ (Markdown: https://insights.sbomify.com/CVE-2025-64443/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64443
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64443
- OSV: https://osv.dev/vulnerability/CVE-2025-64443

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64443/
Summaries are generated and may contain mistakes; the official description above is the record.