INCIDENT MAP

Browse / MCP and Tool Server Flaws / CVE-2026-33252

Cross-Site Tool Execution for HTTP Servers without Authorizatrion in github.com/modelcontextprotocol/go-sdk

CVE-2026-33252 · 2026-03-19 high

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Cross-site request forgery
Affected
github.com/modelcontextprotocol/go-sdk (Go)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

The HTTP transport accepts cross-site POST requests without checking Origin or requiring a JSON content type, so a web page can trigger MCP tool calls. (Our summary, written by a model. The source text is below.)

Details

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.

Impact:

A malicious website may have been able to send cross-site POST requests with Content-Type: text/plain, which due to CORS-safelisted properties would reach the MCP message handling without any CORS preflight barrier.

Fix:

The SDK was modified to perform Content-Type header validation for POST requests and introduced a configurable protection for verifying the origin of the request in commit a433a83. Users are advised to update to v1.4.1 to use this additional protection.

Note: v1.4.1 requires Go 1.25 or later.

Credits:

Thank you to Lê Minh Quân for reporting the issue.

References

Source: GitHub Advisory Database, used under CC BY 4.0.