CVE-2026-33252

MCP Go SDK Allows Cross-Site Tool Execution for HTTP Servers without Authorizatrion

Published Mar 23, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
The Go MCP SDK used Go's standard encoding/json. Prior to version 1.4.1, the Go SDK's Streamable HTTP transport accepted browser-generated cross-site `POST` requests without validating the `Origin` header and without requiring `Content-Type: application/json`. In deployments without Authorization, especially stateless or sessionless configurations, this allows an arbitrary website to send MCP requests to a local server and potentially trigger tool execution. Version 1.4.1 contains a patch for the issue.

Analysis

AI-generated

Technical impact

The Go MCP SDK relied on Go's standard encoding/json library and its Streamable HTTP transport accepted browser‑generated cross‑site POST requests without validating the Origin header or requiring a Content‑Type of application/json. When deployed without authorization—especially in stateless or sessionless configurations—an attacker can host a malicious web page that submits MCP requests to a local server and can cause tools defined by the SDK to execute. This allows an attacker to run arbitrary commands on the host, representing a remote code execution flaw rooted in missing origin validation and improper input handling (CWE‑352 and CWE‑940).

Affected Systems

Affected systems are those using the Modelcontextprotocol Go SDK product, modelcontextprotocol:go-sdk. The vulnerability exists in all versions prior to 1.4.1. Servers running any of those earlier releases in a configuration that does not enforce authorization for the HTTP endpoints are susceptible. The issue applies to any environment that hosts the SDK’s streamable transport and is reachable from a web browser, regardless of operating system.

Risk and Exploitability

The CVSS base score of 7.1 indicates a high severity, and although the EPSS score is not available, the lack of a KEV listing does not diminish the potential danger. Attackers can exploit the flaw by simply loading a malicious page that triggers cross‑site POSTs to the vulnerable endpoint; no special credentials or privileged access are required. Because the server trusts the request without validating the origin, the attack is likely to succeed against users who already have network connectivity to the target server. The risk rises in environments where the SDK is exposed to the internet or to untrusted internal networks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Modelcontextprotocol Go SDK to version 1.4.1 or later to apply the vendor patch.
  • If upgrading is not immediately possible, enforce authentication on the MCP streamable HTTP transport or restrict requests to known origins by configuring server CORS settings.
  • Validate that incoming requests include a Content‑Type header of application/json and check the Origin header before processing.
  • Confirm that HTTP endpoints exposed by the SDK are not publicly accessible or are protected by firewall rules.
  • Continuously monitor hosts running older SDK versions for signs of unauthorized requests or tool execution.

Generated by OpenCVE AI on March 24, 2026 at 13:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-89xv-2j6f-qhc8 Cross-Site Tool Execution for HTTP Servers without Authorizatrion in github.com/modelcontextprotocol/go-sdk
History
Type Values Removed Values Added
First Time appeared Lfprojects
Lfprojects mcp Go Sdk
CPEs cpe:2.3:a:lfprojects:mcp_go_sdk:*:*:*:*:*:*:*:*
Vendors & Products Lfprojects
Lfprojects mcp Go Sdk
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Modelcontextprotocol
Modelcontextprotocol go-sdk
Vendors & Products Modelcontextprotocol
Modelcontextprotocol go-sdk
Type Values Removed Values Added
Description The Go MCP SDK used Go's standard encoding/json. Prior to version 1.4.1, the Go SDK's Streamable HTTP transport accepted browser-generated cross-site `POST` requests without validating the `Origin` header and without requiring `Content-Type: application/json`. In deployments without Authorization, especially stateless or sessionless configurations, this allows an arbitrary website to send MCP requests to a local server and potentially trigger tool execution. Version 1.4.1 contains a patch for the issue.
Title MCP Go SDK Allows Cross-Site Tool Execution for HTTP Servers without Authorizatrion
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

  • CWE-940

    Improper Verification of Source of a Communication Channel

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 24, 2026, 6:39 PM
Reserved
Mar 18, 2026, 2:42 AM
Status
Analyzed
Published
Mar 24, 2026, 12:16 AM
Modified
Jun 17, 2026, 10:37 AM
Severity
Moderate
Public date
Mar 23, 2026, 11:44 PM