CVE-2026-27896: MCP Go SDK Vulnerable to Improper Handling of Case Sensitivity
The Go MCP SDK used Go's standard encoding/json.Unmarshal for JSON-RPC and MCP protocol message parsing in versions prior to 1.3.1. Go's standard library performs case-insensitive matching of JSON keys to struct field tags — a field tagged json:"method" would also match "Method", "METHOD", etc. This violated the JSON-RPC 2.0 specification, which defines exact field names. A malicious MCP peer may have been able to send protocol messages with non-standard field casing that the SDK would silently accept. This had the potential for bypassing intermediary inspection and coss-implementation inconsistency. Go's standard JSON unmarshaling was replaced with a case-sensitive decoder in commit 7b8d81c. Users are advised to update to v1.3.1 to resolve this issue.
Other sources
The Go MCP SDK used Go's standard encoding/json.Unmarshal for JSON-RPC and MCP protocol message parsing. Go's standard library performs case-insensitive matching of JSON keys to struct field tags — a field tagged json:"method" would also match "Method", "METHOD", etc. Additionally, Go's standard library folds the Unicode characters ſ (U+017F) and K (U+212A) to their ASCII equivalents s and k, meaning fields like "paramſ" would match "params". This violated the JSON-RPC 2.0 specification, which defines exact field names.
Impact:
A malicious MCP peer may have been able to send protocol messages with non-standard field casing (e.g., "Method" instead of "method") that the SDK would silently accept. This had the potential for: - Bypassing intermediary inspection: Proxies or policy layers that matched on exact field names may have failed to detect or filter these messages. - Cross-implementation inconsistency: Other MCP SDKs (TypeScript, Python) use case-sensitive parsing and would reject the same messages, creating potential security-boundary confusion.
Fix:
Go's standard JSON unmarshaling was replaced with a case-sensitive decoder (github.com/segmentio/encoding) in commit 7b8d81c. Users are advised to update to v1.3.1 to resolve this issue.
Credits: MCP Go SDK thanks Francesco Lacerenza (Doyensec) for reporting this issue.
— GitHub
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/modelcontextprotocol/go-sdkto a version that resolves this vulnerability.Fixed in 1.3.1 - Upgrade
Upgrade
Go MCP SDKto a version that resolves this vulnerability.Fixed in 1.3.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 7b8d81c
Event History
Frequently Asked Questions
What is the severity of CVE-2026-27896?
CVE-2026-27896 is classified as a moderate severity vulnerability due to improper handling of case sensitivity in JSON key matching.
How do I fix CVE-2026-27896?
To fix CVE-2026-27896, upgrade to version 1.3.1 or later of the Go MCP SDK.
What versions of the Go MCP SDK are affected by CVE-2026-27896?
Versions of the Go MCP SDK prior to 1.3.1 are affected by CVE-2026-27896.
What is the nature of the vulnerability in CVE-2026-27896?
CVE-2026-27896 involves improper handling of case sensitivity which can lead to unexpected behavior in JSON-RPC and MCP protocol message parsing.
Is there a workaround for CVE-2026-27896?
There are no known workarounds for CVE-2026-27896; updating to the fixed version is recommended.