{"id":"GHSA-wvj2-96wp-fq3f","revision":"6c46ee7bdadd400bbd1f4ffb854da50e","records":[{"revision":"6c46ee7bdadd400bbd1f4ffb854da50e","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-wvj2-96wp-fq3f","aliases":["CVE-2026-27896","GO-2026-4569"],"title":"MCP Go SDK Vulnerable to Improper Handling of Case Sensitivity","description":"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.\n\n#### Impact:\n\nA 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:\n  - **Bypassing intermediary inspection:** Proxies or policy layers that matched on exact field names may have failed to detect or filter these messages.\n  - **Cross-implementation inconsistency:** Other MCP SDKs (TypeScript, Python) use case-sensitive parsing and would reject the same messages, creating potential security-boundary confusion.\n\n####  Fix:\n\nGo'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.\n\n#### Credits:\nMCP Go SDK thanks Francesco Lacerenza (Doyensec) for reporting this issue.","state":0,"publishedAt":"2026-02-26T22:20:08+00:00","modifiedAt":"2026-09-10T03:50:36.1395245+00:00","affected":[{"ecosystem":"Go","name":"github.com/modelcontextprotocol/go-sdk","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.3.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/modelcontextprotocol/go-sdk/security/advisories/GHSA-wvj2-96wp-fq3f","https://nvd.nist.gov/vuln/detail/CVE-2026-27896","https://github.com/modelcontextprotocol/go-sdk/commit/7b8d81c264074404abdf5aa16e2cf0c2d9c64cc0","https://github.com/modelcontextprotocol/go-sdk"],"sourceUrl":"https://github.com/advisories/GHSA-wvj2-96wp-fq3f","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-wvj2-96wp-fq3f","identifiers":["GHSA-wvj2-96wp-fq3f","CVE-2026-27896","GO-2026-4569"]},"retained":false,"historicalAffected":[]}],"coverage":[]}