Tech news / read across sources

Bytewire

Home / Software & Apps

Go 1.27.4 fixes 12 security bugs, and eleven of them are in the toolchain, not the runtime

Go 1.27.4 and 1.26.11 shipped November 10. Almost every fix concerns cgo and linker handling at build time, which changes who needs to hurry.

Section
Software & Apps
Published
Read
4 min
Sources
3
Photo: NPS Photo, public domain, via Wikimedia Commons / Wikimedia Commons, Public domain

Go 1.27.4 and Go 1.26.11 came out on November 10, and according to the Go team’s announcement, as forwarded to the oss-security list, they fix 12 security issues. Eleven of the twelve are in the go command, the compiler, the linker or cgo. Only one touches a package that ships inside your programs. That split decides who has to move this week.

Mostly a build-time story

The official release history lists security fixes in cgo, the go command, the compiler, the linker and net/http for both releases, and names no CVE identifiers. The announcement fills in the detail. The tool-related bugs share a theme: ways that source code, a module or an object file you build could smuggle flags or directives into the C compiler and linker that cgo invokes, ending in code execution when the project is built or linked. A few examples from the list:

  • Code execution at build time through certain cgo compiler flags (CVE-2026-97033).
  • Code execution at link time through untrusted GCC spec files found in cgo linker search directories (CVE-2026-97034).
  • A bypass of the #cgo pkg-config: flag allowlist that could load untrusted .pc files or inject flags (CVE-2026-97039).
  • Flag and directive injection via crafted .syso files, which two entries describe (CVE-2026-97038 and CVE-2026-97040).
  • Linker flag injection through //go:cgo_* directives on ELF platforms, and through crafted DLL names on Windows (CVE-2026-97041 and CVE-2026-97042).

Most of these were found by the Go Security Team’s own internal audit, which is itself informative: the team went looking at the cgo boundary and found a cluster. Outside reporters credited include RyotaK of GMO Flatt Security for two and Ali Sherif for a Darwin linker case.

The one runtime-side fix, CVE-2026-97054, is an HTTP/1 server crash in net/http caused by a race in how headers are handled when MaxBytesReader’s limit is exceeded. Jakub Ciolek reported it.

Why “build time” still matters

It is tempting to read “needs a malicious package” and relax. Two groups should not.

CI systems that build code you do not fully control. If your pipeline builds pull requests from forks, vendors third-party modules that use cgo, or compiles customer-supplied projects, the build machine is the target. The usual defense is a sandbox; these fixes close holes in the toolchain’s own guard rails.

Developers on laptops. go build and go run on a freshly cloned repository of unknown origin was always a trust decision, and the bugs fixed here widen what a hostile repository could do with it. Updating the compiler is cheap.

The net/http crash is the opposite case: it matters only to servers using MaxBytesReader, but it requires you to rebuild and redeploy the binary. Updating Go on a laptop does nothing for a binary already running in production.

The second batch in five weeks

This is not the first Go patch release this autumn to carry a pile of fixes. LinuxSecurity reported that Go 1.27.2 and 1.26.9 arrived on October 8 with corrections for 15 security flaws. That batch leaned the other way, toward runtime behavior: server crashes, resource exhaustion, an HTTP/2 crash, and a connection-handling error in which a rejected CONNECT request could leave stray bytes on a pooled connection so the next caller got another user’s response. LinuxSecurity’s advice then applies now too: older executables do not gain library fixes unless you rebuild them, so track rebuilds and deployments rather than only compiler upgrades, and use govulncheck to see what your code actually calls.

I did not read the notes for any release between the two, so this is not a full count for the autumn.

A short upgrade plan

  1. Update build images and local toolchains to 1.27.4, or 1.26.11 if you are on the older line, and confirm with go version in CI logs.
  2. Rebuild and redeploy anything that serves HTTP/1 with request-body limits.
  3. Run govulncheck against both source and binaries.
  4. Where you build untrusted code with cgo, check that the job runs with no secrets and no network beyond what it needs.

For the release notes themselves, Go’s page links the milestone queries for both versions, and says the change log has the full details.

Sources

  1. Go: Release History (go1.27.4 and go1.26.11, released 2026-11-10) go.dev
  2. oss-security: [security] Go 1.27.4 and Go 1.26.11 are released (Go team announcement) openwall.com
  3. LinuxSecurity: Go security update fixes 15 flaws (Go 1.27.2 and 1.26.9) linuxsecurity.com