CVE-2026-34742
The Go MCP SDK used Go's standard encoding/json. Prior to version …
The Go MCP SDK used Go's standard encoding/json. Prior to version 1.4.0, the Model Context Protocol (MCP) Go SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication with StreamableHTTPHandler or SSEHandler, a malicious website could exploit DNS rebinding to bypass same-origin policy restrictions and send requests to the local MCP server. This could allow an attacker to invoke tools or access resources exposed by the MCP server on behalf of the user in those limited circumstances. This issue has been patched in version 1.4.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/modelcontextprotocol/go-sdk/security/advisories/GHSA-xw59-hvm2-8pj6
- github.com/advisories/GHSA-xw59-hvm2-8pj6
- github.com/modelcontextprotocol/go-sdk/commit/67bd3f2e2b53ce11a16db8d976cdb8ff1e986b6d
- github.com/modelcontextprotocol/go-sdk/pull/760
- github.com/modelcontextprotocol/go-sdk/releases/tag/v1.4.0
- nvd.nist.gov/vuln/detail/CVE-2026-34742
- access.redhat.com/errata/RHSA-2026:21772
- access.redhat.com/security/cve/CVE-2026-34742
- nvd.nist.gov/vuln/detail/CVE-2026-34742
- cve.org/CVERecord?id=CVE-2026-34742
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.