Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-97034

Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go

No exploitation reported by the sources we read.

  • Published2026-11-11
  • Fixed in1.27.4 · 1.26.11
  • WeaknessCWE-77

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1103:13CVE publishedCNA

Versions per branch

OSV
toolchain
BranchAffectedFixed in
1.27≥ 1.27.0-0, < 1.27.41.27.4
1.26< 1.26.111.26.11

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As Go, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Go toolchain cmd/goother versions: not affected

    package cmd/gohttps://pkg.go.dev

    Affected
    • < 1.26.11fixed in 1.26.11semver
    • ≥ 1.27.0-0, < 1.27.4fixed in 1.27.4semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-11

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • gccAzure Linux:3all versions · no fixed version listedand 3 other packages
  • goAlpine:v3.24all versions · fixed in 1.26.11-r0
  • go1.26SUSE:Linux Enterprise Server for SAP Applications 15 SP6all versions · fixed in 1.26.11-150000.1.39.1
  • go1.26SUSE:Linux Enterprise Server for SAP Applications 15 SP5all versions · fixed in 1.26.11-150000.1.39.1
  • go1.26SUSE:Linux Enterprise Server for SAP Applications 15 SP4all versions · fixed in 1.26.11-150000.1.39.1
  • go1.26SUSE:Linux Enterprise Server 15 SP6-LTSSall versions · fixed in 1.26.11-150000.1.39.1
  • go1.26SUSE:Linux Enterprise Server 15 SP5-LTSSall versions · fixed in 1.26.11-150000.1.39.1
  • go1.26SUSE:Linux Enterprise Server 15 SP4-LTSSall versions · fixed in 1.26.11-150000.1.39.1

35 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update toolchain to 1.27.4 · 1.26.11

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2026-11-11
Last Modified
2026-11-16
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-775q-r7gv-cr2x

Frequently asked questions

What is CVE-2026-97034?

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.

Is CVE-2026-97034 actively exploited?

Active exploitation of CVE-2026-97034 has not been confirmed. Its EPSS score was 0.3% on 2026-11-15, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-97034?

CVE-2026-97034 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running Go? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record