Skip to main content
VulnerabilityPublished

CVE-2026-97040: Go toolchain cmd/go · Code Injection

Affects Go toolchain cmd/goSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 1.27.4 or 1.26.11 when convenient.

Data as of 11 Nov 2026, 03:33 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 1.27.4, 1.26.11

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade cmd/go and cmd/link to 1.27.4 or 1.26.11.

Affected software

ProductAffectedFixed in
Go toolchaincmd/goAffected
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.27.4
Go toolchaincmd/goAffected
  • <1.26.11
Fixed in
  • 1.26.11
Go toolchaincmd/linkAffected
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.27.4
Go toolchaincmd/linkAffected
  • <1.26.11
Fixed in
  • 1.26.11
Gocmd/gopkg:golang/cmd/goOther threatsAffected
  • <1.26.11
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.26.11
  • 1.27.4
Gocmd/linkpkg:golang/cmd/linkOther threatsAffected
  • <1.26.11
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.26.11
  • 1.27.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Building a package containing a crafted ".syso" file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading ".syso" entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A ".syso" file beginning with a "go object" header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as "cgo_ldflag" or "cgo_dynamic_linker") embedded in the ".syso" file to be passed to the external linker without validation. Additionally, ".syso" filenames longer than 16 bytes lost their ".syso" extension when truncated in archive headers, and unrecognized ".syso" formats forced external linking in pure-Go builds. The linker now rejects ".syso" files that are not recognized host object formats, and "cmd/go" and "cmd/pack" preserve the ".syso" suffix when truncating long archive member names.

References

Community reviews

Loading reviews…