Building a malicious package that uses cgo could cause arbitrary code execution at build time through several compiler
Source GCVE Database
Not known to be exploited : upgrade to 1.27.4 or 1.26.11 soon.
Data as of 11 Nov 2026, 08:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.27.4, 1.26.11
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 to 1.27.4 or 1.26.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Go toolchaincmd/go | Affected
| Fixed in
|
| Go toolchaincmd/go | Affected
| Fixed in
|
Gocmd/gopkg:golang/cmd/goOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability has been mitigated by disallowing the use of "--sysroot" and "-target" flags in "#cgo" directives, verifying that "-isysroot" and "-Wl,-syslibroot" flags do not point to regular files, and restricting the "-x" flag to only the C, C++, Objective-C, and assembler languages supported by cgo. Users should ensure they are using a version of the build tools or cgo implementation that includes these restrictions.
Description
A vulnerability in the cgo build process allows malicious packages to execute arbitrary code at build time by exploiting certain compiler and linker flags in "#cgo" directives. Flags such as "--sysroot" and "-target" could be abused to redirect compiler components or execute helper tools from attacker-controlled locations. Restrictions have been applied to disallow or validate these flags to prevent exploitation.