UNKNOWNCVSS not yet scoredVulnerability

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.

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-11T23:49:45.533241+00:00
Epss score
0.0028
Cve id
CVE-2026-97034
First seen by Signal
2026-11-11T07:36:44+00:00
Name
CVE-2026-97034
Retrieved at
2026-11-11T23:51:16+00:00
Published at
2026-11-11T05:19:57.397
Last modified
2026-11-11T05:19:57.397
Epss percentile
0.20669

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-97034 — Ninja Signal Threat Intelligence | Ninja Signal