Most recent entries from all

bdu:2026-02402

2026-10-03T02:48:48.500448+00:00

bdu:2026-02402

CLEANSTART-2026-DZ42058 — Security fix for CVE-2026-27896 applied in: gptscript 0.9.8-r0

2026-10-03T02:48:48.500493+00:00

Affected: CleanStart: gptscript

Security vulnerability affects the gptscript package. This issue is resolved in later releases. See references for vulnerability details.

EUVD-2026-369294

2026-10-03T02:48:48.500526+00:00

EUVD-2026-369294

fkie_cve-2026-27896

2026-10-03T02:48:48.500539+00:00

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.

GHSA-wvj2-96wp-fq3f — MCP Go SDK Vulnerable to Improper Handling of Case Sensitivity

2026-10-03T02:48:48.500570+00:00

Affected: Go: github.com/modelcontextprotocol/go-sdk

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.