Go toolchain cmd/go
Unexpected code execution via escaped quotes in //go:cgo_ldflag in cmd/go and cmd/compile
Building a malicious package that uses cgo could bypass "#cgo LDFLAGS" validation and cause unexpected code execution at build time, or cause the go command to panic, via crafted quoting in "//go:cgo_ldflag" directives. When "cmd/cgo" generates "_cgo_gotypes.go", it quotes each "#cgo LDFLAGS" argument with strconv.Quote in a "//go:cgo_ldflag" directive, but "cmd/compile" and "cmd/go" parsed those directives by splitting on raw quote characters without handling backslash escapes or unquoting the string. This mismatch allowed disallowed linker flags or unvalidated linker search paths to be smuggled past the go command's flag checks and passed to the external linker. In addition, deduplicating LDFLAGS in the go command could panic with an out-of-bounds slice index when a prefix of the flag list matched near the end of the slice. "cmd/compile" and "cmd/go" now properly handle backslash-escaped quotes and unquote "//go:cgo_*" pragma strings with strconv.Unquote, and the slice bounds check in processCgoOutputs has been fixed.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.26.11
- >= 1.27.0-0, < 1.27.4
Fixed in 1.26.11, 1.27.4
- < 1.26.11
- >= 1.27.0-0, < 1.27.4
Fixed in 1.26.11, 1.27.4
Mitigation
Upgrade cmd/go to 1.26.11 or 1.27.4 or later.
Upgrade cmd/compile to 1.26.11 or 1.27.4 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.