CVE-2026-97034
Last modified
CVE-2026-97034 is a vulnerability of currently unknown severity. 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*". EPSS estimates a 0.28% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Go toolchain | cmd/go | < 1.26.11; >= 1.27.0-0, < 1.27.4 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-97034?
How severe is CVE-2026-97034?
How do I fix CVE-2026-97034?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97029Flatpak's process ID namespace separation does not prevent a…5.7
- CVE-2026-9703Grafana's data source proxy did not apply role-based access …7.1
- CVE-2026-97030A trusted template author may have previously written a vali…6.1
- CVE-2026-97031Multiple ECH outer extension references are not permitted un…7.5
- CVE-2026-97032HTTP/2 servers could end up crashing due to inadvertently mo…7.5
- CVE-2026-97033Building a malicious package that uses cgo could cause arbit…
- CVE-2026-97035When using Clang or GCC, building a malicious package that u…
- CVE-2026-97036On Darwin, building a malicious package that uses cgo could …
- CVE-2026-97037Building a malicious package that uses cgo could cause arbit…
- CVE-2026-97038Building a malicious package containing ".syso" files or cgo…
- CVE-2026-97039Building a malicious package that uses "#cgo pkg-config:" di…
- CVE-2026-9704A flaw was found in Keycloak. An authenticated user with low…8.8
Are you affected by CVE-2026-97034?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
