How severe is CVE-2025-64443?

No CVSS score has been assigned to CVE-2025-64443 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-64443?

CVE-2025-64443 affects the following packages: github.com/docker/mcp-gateway (Go). Ecosystems affected: Go.

How do I fix CVE-2025-64443?

Update github.com/docker/mcp-gateway to 0.28.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64443 is resolved across your whole dependency graph.

How do I detect CVE-2025-64443 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/docker/mcp-gateway, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-64443 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-64443 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-64443 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-64443?

CVE-2025-64443 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-64443?

CVE-2025-64443 is classified as CWE-749 (CWE-749). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-64443 published, and has it been updated?

CVE-2025-64443 was published on December 3, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-64443 — mcp-gateway

Fix: docker/mcp-gateway@6b076b2

CVE-2025-64443 is a CWE-749 vulnerability in github.com/docker/mcp-gateway. A fix is available for github.com/docker/mcp-gateway — see the affected versions and patch details below.

DNS Rebinding vulnerability present when running MCP Gateway in sse or streaming mode

Also known asGHSA-46gc-mwh4-cc5rGO-2025-4179

Published

Dec 3, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64443.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/docker/mcp-gateway

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/docker/mcp-gateway`	all versions	0.28.0`go get github.com/docker/mcp-gateway@v0.28.0`

Affected Products

1 product · 1 configurations

Application

mcp gatewaydocker

< 0.28.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/docker/mcp-gateway, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/docker/mcp-gateway to 0.28.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64443 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 availabl

O3 Security · Impact-Aware SCA

Is CVE-2025-64443 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works