CVE-2026-27896

CVE-2026-27896 is a high-severity vulnerability in Lfprojects Mcp Go Sdk with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-178.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-27896?
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.
How severe is CVE-2026-27896?
CVE-2026-27896 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-27896 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-27896?
CVE-2026-27896 affects Lfprojects Mcp Go Sdk. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-27896?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-27896 have an EU (EUVD) identifier?
Yes. CVE-2026-27896 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-8792.
When was CVE-2026-27896 published?
CVE-2026-27896 was published on 2026-02-26 and last updated on 2026-06-30.

References

Affected products (1)

More vulnerabilities in Lfprojects Mcp Go Sdk

All CVEs affecting Lfprojects Mcp Go Sdk →

Other CWE-178 vulnerabilities

Browse all CWE-178 vulnerabilities →