CVE-2026-27896
The Go MCP SDK used Go's standard encoding/json.Unmarshal for …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/modelcontextprotocol/go-sdk/commit/7b8d81c264074404abdf5aa16e2cf0c2d9c64cc0
- github.com/modelcontextprotocol/go-sdk/security/advisories/GHSA-wvj2-96wp-fq3f
- nvd.nist.gov/vuln/detail/CVE-2026-27896
- github.com/advisories/GHSA-wvj2-96wp-fq3f
- access.redhat.com/security/cve/CVE-2026-27896
- bugzilla.redhat.com/show_bug.cgi?id=2442903
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27896.json
- nvd.nist.gov/vuln/detail/CVE-2026-27896
- cve.org/CVERecord?id=CVE-2026-27896
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.