mediumresolved

MCP fetch hostname normalization bypasses private-address guard

The address guard and HTTP client interpret internationalized hostnames differently. An attacker-controlled domain can exploit that disagreement to direct the fetch tool to a private destination despite the public-address check.

The address guard and HTTP client interpret internationalized hostnames differently. An attacker-controlled domain can exploit that disagreement to direct the fetch tool to a private destination despite the public-address check.

This is a maintainer-documented vulnerability disclosure, not evidence of exploitation against a named customer. Affected ranges: mcp-server-fetch >= 2026.10.10, <= 2026.10.19. The maintainer lists patched releases: mcp-server-fetch 2026.10.24.

Takeaway

Check the deployed package and its configuration against the advisory. Apply the listed fix on a supported release line and verify the trust boundary with an untrusted client or repository.

Sources

mcpghsa-v38p-wf49-hx2j