CVE-2026-97034 Affecting go package, versions <1.26.11-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.28% (21st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALPINE324-GO-22526272
  • published13 Nov 2026
  • disclosed11 Nov 2026

Introduced: 11 Nov 2026

NewCVE-2026-97034  (opens in a new tab)

How to fix?

Upgrade Alpine:3.24 go to version 1.26.11-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream go package and not the go package as distributed by Alpine. See How to fix? for Alpine:3.24 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1