CVE-2026-97037: Linker script injection via split -Wl, flags and Darwin or symbol linker flags in cgo in cmd/go
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Fixed version: Go toolchain cmd/go 1.26.11, 1.27.4; azl3 gcc 13.2.0-7 on Azure Linux 3.0 Release Notes; azl3 golang 1.26.10-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Go toolchain cmd/go 1.26.11, 1.27.4; azl3 gcc 13.2.0-7 on Azure Linux 3.0 Release Notes; azl3 golang 1.26.10-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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".
- Published
- Nov 11, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-94
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go toolchain cmd/go
- before 1.26.11affected · semver
- 1.27.0-0 and later · before 1.27.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | go | before 1.26.11-r0 | 1.26.11-r0 |
| Debian:12 | golang-1.19 | from 0 | — |
| Debian:13 | golang-1.24 | from 0 | — |
| Debian:14 | golang-1.26 | before 1.26.11-1 | 1.26.11-1 |
| Debian:14 | golang-1.27 | before 1.27.4-1 | 1.27.4-1 |
| Go | toolchain | from 1.27.0-0 · before 1.27.4 | 1.27.4 |
| Go | toolchain | before 1.26.11 | 1.26.11 |
| openSUSE:Tumbleweed | go1.26 | before 1.26.11-1.1 | 1.26.11-1.1 |
| openSUSE:Tumbleweed | go1.27 | before 1.27.4-1.1 | 1.27.4-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | go1.26 | before 1.26.11-150000.1.39.1 | 1.26.11-150000.1.39.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | go1.27 | before 1.27.4-150000.1.18.1 | 1.27.4-150000.1.18.1 |
Same product
go toolchain: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-24531Output of "go env" does not sanitize values in cmd/go39Monitor
- CVE-2024-45340GOAUTH credential leak in cmd/go35Monitor
- CVE-2026-56865Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-97035Nov 11, 2026 · Unexpected code execution and arbitrary file write via Clang -gen-* and GCC -gnat* flags in cgo in cmd/go0Monitor
- ← EarlierCVE-2026-97036Nov 11, 2026 · Arbitrary code execution during build on darwin via "-l to_library" in cgo in cmd/go0Monitor
- Later →CVE-2026-97038Nov 11, 2026 · Arbitrary code execution via crafted .syso files and cgo linker input files in cmd/go0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go toolchain cmd/go | 1.26.11 | Vendor (CNA) |
| Go toolchain cmd/go | 1.27.4 | Vendor (CNA) |
| azl3 gcc 13.2.0-7 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 golang 1.26.10-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 golang 1.26.11-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 golang 1.27.3-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 golang 1.27.4-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 tensorflow 2.16.1-11 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| alpine:go | 1.26.11-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:golang-1.26 | 1.26.11-1 · Debian:14 | Package registry (OSV) |
| debian:golang-1.27 | 1.27.4-1 · Debian:14 | Package registry (OSV) |
| Go:toolchain | 1.26.11 | Package registry (OSV) |
| Go:toolchain | 1.27.4 | Package registry (OSV) |
| opensuse:go1.26 | 1.26.11-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.27 | 1.27.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:go1.26 | 1.26.11-150000.1.39.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:go1.27 | 1.27.4-150000.1.18.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Fix recordedsame day
- Published
- TodayNov 16, 2026+5 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-970380 days apartArbitrary code execution via crafted .syso files and cgo linker input files in cmd/go0Monitor
- CVE-2026-970400 days apartCgo directive injection via .syso files disguised as Go object files in cmd/go and cmd/link0Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.