Golang 1.10: When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at
Affects golang-1.10Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 18 Nov 2026, 15:19 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 8.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10golang-1.26pkg:deb/ubuntu/golang-1.26?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10golang-1.27pkg:deb/ubuntu/golang-1.27?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.23pkg:deb/ubuntu/golang-1.23?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.25pkg:deb/ubuntu/golang-1.25?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.26pkg:deb/ubuntu/golang-1.26?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files ("specs" or "*.spec"). When linking with "-fopenmp", "-fopenacc", or "-fsanitize=" in "#cgo LDFLAGS", GCC's built-in link spec evaluates "%:include(libgomp.spec)" or "%:include(libsanitizer.spec)" and searches for spec files in "-L" and sysroot directories (including subdirectories and multilib sibling directories such as "../lib64"), as well as the working directory when "-fopenmp" or "-fopenacc" is used or when "-fsanitize=" is combined with "-static" or "-static-lib*". The go command now rejects "-L", "-isysroot", and "-Wl,-syslibroot" directories (and the working and package directories when applicable) that contain GCC spec files, and disallows "@" and "-" prefixes in "-fsanitize=" compiler flag values.
References
- ubuntu.com/security/CVE-2026-97034 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-97034 (opens in a new tab)
- groups.google.com/g/golang-announce/c/iY8TY0wWgbM/m/KsU1KfWgAQAJ (opens in a new tab)
- github.com/golang/go/issues/82576 (opens in a new tab)
- github.com/golang/go/commit/c5426cee10abdae95f8f86e22bfff0932c75be79 (opens in a new tab)
- github.com/golang/go/commit/faaa8b62d6d8b08ff164213508cad1be33149ec7 (opens in a new tab)
- go.dev/cl/862147 (opens in a new tab)
- go.dev/issue/82576 (opens in a new tab)
- groups.google.com/g/golang-announce/c/iY8TY0wWgbM (opens in a new tab)
- pkg.go.dev/vuln/GO-2026-6857 (opens in a new tab)