Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-97034
PublishedWhen 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.
- Source published
- 11 Nov 2026 03:13:17 UTC
- Source modified
- 11 Nov 2026 03:13:17 UTC
- Saved here
- 11 Nov 2026 04:25:37 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
euvd · EUVD-2026-123111
PublishedWhen 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Nov 11, 2026, 3:13:17 AM
dateUpdated: Nov 11, 2026, 3:13:17 AM
4 related source bulletins · separate from aliases
openSUSE-SU-2026:12540-1: go1.27-1.27.4-1.1 on GA media
CVE-2026-97033 · CVE-2026-97034 · CVE-2026-97035 · CVE-2026-97036 · CVE-2026-97037 · CVE-2026-97038 · CVE-2026-97039 · CVE-2026-97040 · CVE-2026-97041 · CVE-2026-97042 · CVE-2026-97043 · CVE-2026-97054
WID-SEC-W-2026-4370: Golang Go: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff
CVE-2026-97033 · CVE-2026-97034 · CVE-2026-97035 · CVE-2026-97036 · CVE-2026-97037 · CVE-2026-97038 · CVE-2026-97039 · CVE-2026-97040 · CVE-2026-97041 · CVE-2026-97042 · CVE-2026-97043 · CVE-2026-97054
openSUSE-SU-2026:12529-1: go1.26-1.26.11-1.1 on GA media
CVE-2026-97033 · CVE-2026-97034 · CVE-2026-97035 · CVE-2026-97036 · CVE-2026-97037 · CVE-2026-97038 · CVE-2026-97039 · CVE-2026-97040 · CVE-2026-97041 · CVE-2026-97042 · CVE-2026-97043 · CVE-2026-97054
msrc_CVE-2026-97034: Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go
CVE-2026-97034
- Source published
- Nov 11, 2026, 3:13:17 AM (timezone not stated)
- Source modified
- Nov 11, 2026, 3:13:17 AM (timezone not stated)
- Saved here
- 15 Nov 2026 05:33:26 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
nvd · CVE-2026-97034
PublishedWhen 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Awaiting Analysis
Original publisher date fields
published: 2026-11-11T05:19:57.397
lastModified: 2026-11-12T22:09:39.233
- Source published
- 11 Nov 2026 05:19:57 UTC
- Source modified
- 12 Nov 2026 22:09:39 UTC
- Saved here
- 13 Nov 2026 06:18:20 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
osv · GO-2026-6857
PublishedWhen 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.
- Source published
- 11 Nov 2026 02:51:11 UTC
- Source modified
- 11 Nov 2026 03:15:14 UTC
- Saved here
- 11 Nov 2026 04:27:36 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.