DNS Rebinding Protection Disabled by Default in Model Context Protocol Go SDK for Servers Running on Localhost
CVE-2026-34742 · GHSA-xw59-hvm2-8pj6 · published 2026-04-01 · updated 2026-07-21
- Severity
- High
- CVSS score
- 8.1
- Chance of exploitation (EPSS)
- 0.47%
- Fixed in
- 1.4.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
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.
Upgrade github.com/modelcontextprotocol/go-sdk to 1.4.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| github.com/modelcontextprotocol/go-sdk | Go | < 1.4.0 | 1.4.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- HighCross-Site Tool Execution for HTTP Servers without Authorizatrion in github.com/modelcontextprotocol/go-sdkgithub.com/modelcontextprotocol/go-sdk
- HighImproper handling of null Unicode character when parsing JSON in github.com/modelcontextprotocol/go-sdkgithub.com/modelcontextprotocol/go-sdk
- HighMCP Go SDK Vulnerable to Improper Handling of Case Sensitivitygithub.com/modelcontextprotocol/go-sdk
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.