CVE-2026-34742: Model Context Protocol Go SDK: DNS Rebinding Protection Disabled by Default for Servers Running on Localhost
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.
Security readout for executives and security teams
Plain-English summary
This issue affects Go applications using the Model Context Protocol Go SDK before 1.4.0. If a local, unauthenticated HTTP MCP server uses affected handlers, a malicious website visited by the user could reach that local service and misuse tools or resources it exposes.
Executive priority
Treat as high priority where MCP servers run locally and expose sensitive automation or data. Patch quickly, but prioritize confirmed unauthenticated localhost HTTP deployments over unaffected SDK usage.
Technical view
Before v1.4.0, the MCP Go SDK did not enable DNS rebinding protection by default for HTTP-based localhost servers using StreamableHTTPHandler or SSEHandler without authentication. The CVSS vector requires user interaction and high attack complexity, but allows high confidentiality and integrity impact.
Likely exposure
Exposure is limited to deployments using modelcontextprotocol/go-sdk versions before 1.4.0, running HTTP-based MCP servers on localhost without authentication through StreamableHTTPHandler or SSEHandler.
Exploitation context
The source bundle does not cite active exploitation or KEV listing. Exploitation requires a user to visit a malicious website, and depends on the local MCP server exposing useful tools or resources without authentication.
Researcher notes
Key constraints are localhost HTTP server, no authentication, affected handlers, and go-sdk below 1.4.0. Evidence supports a DNS rebinding class issue, not remote unauthenticated internet exploitation.
Mitigation direction
Upgrade modelcontextprotocol/go-sdk to version 1.4.0 or later.
Enable authentication for local HTTP-based MCP servers.
Review vendor advisory and release notes for current guidance.
Avoid exposing sensitive tools or resources through unauthenticated localhost MCP servers.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1188: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1188 · source CWE mapping
Initialization of a Resource with an Insecure Default
Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.