Is CVE-2026-34742 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34742 being exploited in the wild.

How severe is CVE-2026-34742?

High severity, with a CVSS score of 8.1, published 2 April 2026.

Which products and versions are affected?

github.com/modelcontextprotocol/go-sdk (Go) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0.

Is there a fix for CVE-2026-34742?

Yes. github.com/modelcontextprotocol/go-sdk (Go): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34742 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-34742?

Check whether you run github.com/modelcontextprotocol/go-sdk (Go) or Lfprojects Mcp Go Sdk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34742: modelcontextprotocol go-sdk DNS rebinding in HTTP handlers

Q: Is there a fix for CVE-2026-34742?

Yes. github.com/modelcontextprotocol/go-sdk (Go): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-34742 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-34742?

Check whether you run github.com/modelcontextprotocol/go-sdk (Go) or Lfprojects Mcp Go Sdk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34742 · Severity: high · CVSS 8.1 · Published 2026-04-02

The Model Context Protocol (MCP) Go SDK, used to build interfaces for AI models, was found to have insecure default settings when running servers on a local machine. A malicious website could trick a user's browser into sending unauthorized commands to a local MCP server, potentially allowing attackers to access private data or execute tools on the user's behalf. This risk primarily affects developers or users running these servers locally without additional authentication.

Technologies: github.com/modelcontextprotocol/go-sdk (Go). Vendors: Go, Lfprojects.

Quick answers

Is CVE-2026-34742 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34742 being exploited in the wild.
How severe is CVE-2026-34742?: High severity, with a CVSS score of 8.1, published 2 April 2026.
Which products and versions are affected?: github.com/modelcontextprotocol/go-sdk (Go) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0.
Is there a fix for CVE-2026-34742?: Yes. github.com/modelcontextprotocol/go-sdk (Go): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34742 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34742?: Check whether you run github.com/modelcontextprotocol/go-sdk (Go) or Lfprojects Mcp Go Sdk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/modelcontextprotocol/go-sdk (Go): upgrade to 1.4.0 or later
```
go get github.com/modelcontextprotocol/go-sdk@v1.4.0
```

Technical details

The Model Context Protocol (MCP) Go SDK is vulnerable to DNS rebinding attacks because it lacks default protection for HTTP-based servers using StreamableHTTPHandler or SSEHandler when bound to localhost. An attacker can exploit this by enticing a user to visit a malicious website, which then uses DNS rebinding to bypass the browser's Same-Origin Policy (SOP) and interact with the local MCP server. If the server is running without authentication, the attacker can invoke exposed tools or access resources. This issue does not affect servers using stdio transport. The vulnerability is addressed in version 1.4.0, which enables DNS rebinding protection by default for localhost bindings.

Affected products

Model Context Protocol (MCP) go-sdk < 1.4.0

Identifiers

CVE-2026-34742
GHSA-xw59-hvm2-8pj6
GO-2026-5771

Timeline

2026-03-30: disclosed
2026-04-01: advisory: GitHub Advisory published
2026-04-02: other: NVD published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.