Dev News Daily ENDE

Go 1.27.4 and 1.26.11 fix eleven ways a cgo build could run code, plus a net/http crash

The Go team released Go 1.27.4 and Go 1.26.11 on 10 November. The release history describes both as security releases with fixes to cgo, the go command, the compiler, the linker and the net/http package, along with bug fixes to the assembler, the compiler, the runtime, toolchain bootstrapping and the crypto/fips140, crypto/hkdf, crypto/rsa, crypto/tls and net packages.

The Go vulnerability database lists twelve new entries, GO-2026-6848 to GO-2026-6859, all fixed in exactly those two versions. Eleven of them are in the toolchain rather than in the standard library, and they share one theme: a package being built with cgo could get the toolchain to do something it was not meant to do.

The entries name the routes. Escaped quotes in a //go:cgo_ldflag directive could lead to unexpected code execution (CVE-2026-97043). Linker flags could be injected through cgo_import_dynamic and PE DLL names (CVE-2026-97042) or through //go:cgo_* directives into the host linker (CVE-2026-97041). .syso files disguised as Go object files could carry cgo directives (CVE-2026-97040), and crafted .syso files and cgo linker input files could lead to arbitrary code execution in cmd/go (CVE-2026-97038). The #cgo pkg-config: directive could bypass flag sanitisation (CVE-2026-97039).

Several entries concern compiler and linker flags that the go command's allow-list let through. Split -Wl, flags and Darwin or symbol linker flags allowed linker script injection (CVE-2026-97037); -l with a to_library argument allowed code execution on Darwin (CVE-2026-97036); Clang -gen- and GCC -gnat flags allowed code execution and arbitrary file writes (CVE-2026-97035); GCC spec files in cgo linker search directories allowed command execution (CVE-2026-97034); and --sysroot, -target, -isysroot, -Wl,-syslibroot and -x led to unexpected code execution (CVE-2026-97033).

The twelfth entry is a runtime problem: an HTTP/1 server could crash because of a race on headers involving MaxBytesReader in net/http (CVE-2026-97054).

Go 1.27.4 and 1.26.11 fix eleven ways a cgo build could run code, plus a net/http crash
Go 1.27.4 and 1.26.11 fix eleven ways a cgo build could run code, plus a net/http crash — Dev News Daily

Why it matters

Eleven of the twelve fixes concern what happens while a package is being built, not while a program runs, and the entry titles speak of flag sanitisation and injected linker flags, so the toolchain is meant to filter what cgo directives can pass. Eleven ways around that filter in one release show how wide the surface is. Anyone who builds third-party code in CI, or in tooling that fetches modules automatically, should treat this update as urgent even if no service of theirs links cgo at runtime.

Primary source
Go release history
https://go.dev/doc/devel/release