AZL-113642: CVE-2026-97043 affecting package tensorflow 2.16.1-11
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:cgoldflag" directives. When "cmd/cgo" generates "cgogotypes.go", it quotes each "#cgo LDFLAGS" argument with strconv.Quote in a "//go:cgoldflag" 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 Software
Event History
Frequently Asked Questions
What would an attacker need to exploit this issue?
An attacker would need to provide a malicious package that uses cgo and contains crafted quoting in //go:cgo_ldflag directives. Exploitation occurs when that package is built.
What are the possible impacts during a vulnerable build?
Crafted directives can smuggle disallowed linker flags or unvalidated linker search paths past go command validation and pass them to the external linker, potentially causing unexpected code execution at build time. The malformed flags can also cause the go command to panic through an out-of-bounds slice index.
What behavior was corrected to address the issue?
cmd/compile and cmd/go now handle backslash-escaped quotes and unquote //go:cgo_* pragma strings with strconv.Unquote. The slice bounds check in processCgoOutputs was also fixed.