Golang 1.10: Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing
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
Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via "#cgo LDFLAGS". Split "-Wl," flags that consume a following argument (such as "-Wl,-rpath", "-Wl,--just-symbols", and "-Wl,-undefined") previously accepted a bare second argument without a "-Wl," prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as "-framework", "-Wl,-framework", "-Wl,-undefined", "-Wl,--just-symbols", "-Wl,-R", "-Wl,-subsystem", and (on non-Darwin platforms) "-Wl,-sectcreate" could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a "-Wl," prefix on the second token of split "-Wl," flags (except "-Wl,-R"), verifies that these flags do not reference linker script files, and disallows bare "-Wl,--warn-backrefs-exclude".
References
- ubuntu.com/security/CVE-2026-97037 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-97037 (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/82573 (opens in a new tab)
- github.com/golang/go/commit/5f05d301a704caf2bda2801edef56196c90c82e2 (opens in a new tab)
- github.com/golang/go/commit/8d42fafae94059ce25ad5d410628535d54ee1680 (opens in a new tab)
- go.dev/cl/862150 (opens in a new tab)
- go.dev/issue/82573 (opens in a new tab)
- groups.google.com/g/golang-announce/c/iY8TY0wWgbM (opens in a new tab)
- pkg.go.dev/vuln/GO-2026-6854 (opens in a new tab)