When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via
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:03 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 Go toolchain has implemented mitigations by rejecting directories containing GCC spec files in "-L", "-isysroot", and "-Wl,-syslibroot" flags and disallowing certain prefixes in "-fsanitize=" compiler flags. Users should update to a Go version that includes these mitigations. No additional action is specified or required beyond using the updated Go toolchain.
Description
A vulnerability in GCC's handling of cgo packages allows arbitrary command execution at link time via untrusted GCC spec files. This occurs when linking with certain flags (-fopenmp, -fopenacc, or -fsanitize=) that cause GCC to evaluate and include spec files from directories that may be untrusted. The Go toolchain now rejects directories containing such spec files and disallows certain flag prefixes to mitigate this risk.