Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Go

CVE-2026-97041: Host linker flag injection via //go:cgo_* directives in cmd/compile and cmd/link

—No exploit Fix available

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.23% (FIRST EPSS).
  • Fixed version: Go toolchain cmd/compile 1.26.11, 1.27.4; Go toolchain cmd/link 1.26.11, 1.27.4; azl3 golang 1.26.10-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Go toolchain cmd/compile 1.26.11, 1.27.4; Go toolchain cmd/link 1.26.11, 1.27.4; 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 containing "//go:cgo_*" compiler directives could inject arbitrary flags into the external linker invocation on ELF platforms. The compiler and linker did not reject commas in "//go:cgo_import_dynamic", "//go:cgo_export_dynamic", "//go:cgo_export_static", "//go:cgo_import_static", and "//go:cgo_dynamic_linker" directives, and the linker passed the dynamic linker path using "-Wl,--dynamic-linker,<path>". Furthermore, the two-argument form of "//go:cgo_import_dynamic" (which is permitted in non-cgo Go source files) could overwrite the external symbol name of a symbol already marked for cgo export. A symbol name or dynamic linker path containing a comma or leading "@" could split "-Wl,--export-dynamic-symbol=" or "-Wl,--dynamic-linker," into arbitrary host linker flags or response file arguments. The compiler and linker now reject commas in "//go:cgo_*" symbol and dynamic linker directives, the linker passes "-Wl,--dynamic-linker=<path>", and "cgo_import_dynamic" no longer overwrites symbols exported via "cgo_export_dynamic" or "cgo_export_static".

Published
Nov 11, 2026
Updated
Nov 12, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

0

Monitor

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.

Follow CVE-2026-97041

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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/compile

    • before 1.26.11affected · semver
    • 1.27.0-0 and later · before 1.27.4affected · semver
  • Go toolchain cmd/link

    • 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.

EcosystemPackageAffected rangeFix
Alpine:v3.24gobefore 1.26.11-r01.26.11-r0
Debian:12golang-1.19from 0—
Debian:13golang-1.24from 0—
Debian:14golang-1.26before 1.26.11-11.26.11-1
Debian:14golang-1.27before 1.27.4-11.27.4-1
Gotoolchainfrom 1.27.0-0 · before 1.27.41.27.4
Gotoolchainbefore 1.26.111.26.11
openSUSE:Tumbleweedgo1.26before 1.26.11-1.11.26.11-1.1
openSUSE:Tumbleweedgo1.27before 1.27.4-1.11.27.4-1.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7go1.26before 1.26.11-150000.1.39.11.26.11-150000.1.39.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7go1.27before 1.27.4-150000.1.18.11.27.4-150000.1.18.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go toolchain cmd/compile1.26.11Vendor (CNA)
Go toolchain cmd/compile1.27.4Vendor (CNA)
Go toolchain cmd/link1.26.11Vendor (CNA)
Go toolchain cmd/link1.27.4Vendor (CNA)
azl3 golang 1.26.10-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 golang 1.26.11-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 golang 1.27.3-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 golang 1.27.4-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 tensorflow 2.16.1-11 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
alpine:go1.26.11-r0 · Alpine:v3.24Package registry (OSV)
debian:golang-1.261.26.11-1 · Debian:14Package registry (OSV)
debian:golang-1.271.27.4-1 · Debian:14Package registry (OSV)
Go:toolchain1.26.11Package registry (OSV)
Go:toolchain1.27.4Package registry (OSV)
opensuse:go1.261.26.11-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:go1.271.27.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:go1.261.26.11-150000.1.39.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:go1.271.27.4-150000.1.18.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package 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.

  1. Fix recordedsame day
  2. Published
  3. TodayNov 16, 2026+5 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records