CVE-2026-97037VulnerabilityPublished 11 Nov 2026

Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script

Source GCVE Database

Compare

Authoritative record:CVE-2026-97037· High

Not known to be exploited : upgrade to 1.27.4 or 1.26.11 soon.

Data as of 11 Nov 2026, 08:03 UTC

Severity

High

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-f47v-97w8-qc5g

What to do

Upgrade cmd/go to 1.27.4 or 1.26.11.

Affected software

Product	Affected	Fixed in
Go toolchaincmd/go	Affected >=1.27.0-0 <1.27.4	Fixed in 1.27.4
Go toolchaincmd/go	Affected <1.26.11	Fixed in 1.26.11
Gocmd/go`pkg:golang/cmd/go`Other threats	Affected <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.

AI-suggested

The Go command has been updated to enforce stricter validation of linker flags, including requiring "-Wl," prefixes on certain flags, verifying that flags do not reference linker script files, and disallowing specific problematic flags. Users should update to the fixed Go compiler version once available.

Description

A vulnerability in the Go compiler's handling of cgo linker flags could allow arbitrary code execution at link time. This occurs when malicious packages pass specially crafted linker script files via "#cgo LDFLAGS". The issue involves improper handling of split "-Wl," flags that consume a following argument, which could be interpreted as positional input files or linker scripts by the host linker, particularly GNU ld.bfd. The Go command now enforces stricter validation by requiring "-Wl," prefixes on certain flags, verifying that flags do not reference linker script files, and disallowing specific problematic flags.

Impact

If exploited, this vulnerability could allow arbitrary code execution during the link phase of building Go programs that use cgo, potentially compromising the build environment or resulting binaries. However, there is no indication of known exploitation in the wild.

Summary

The vulnerability arises from the Go compiler's cgo feature allowing malicious packages to pass linker script files to the host linker through "#cgo LDFLAGS". Split "-Wl," flags that consume a following argument (e.g., "-Wl,-rpath", "-Wl,--just-symbols", "-Wl,-undefined") previously accepted a bare second argument without the "-Wl," prefix, which the compiler driver passed directly to the linker as a positional input file. Additionally, on GNU ld.bfd, certain flags could cause the linker to interpret their arguments as linker scripts if they named regular files on disk. To mitigate this, the Go command now requires explicit "-Wl," prefixes on the second token of split flags (except "-Wl,-R"), checks that these flags do not reference linker script files, and disallows the bare "-Wl,--warn-backrefs-exclude" flag.

References

Community reviews

Loading reviews…