Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

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

CVE-2026-97034

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (toolchain 1.27.4, 1.26.11), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go toolchain

    Affected
    < 1.26.11>= 1.27.0-0, < 1.27.4
    Fixed in
    1.26.11, 1.27.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record GO-2026-6857

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-97034

Advisory: Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go
IDs: CVE-2026-97034
Record: https://patchnext.com/advisories/cve-2026-97034 (revision 1, source checked 11 Nov 2026, 07:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: toolchain 1.27.4, 1.26.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go toolchain: affected < 1.26.11; >= 1.27.0-0, < 1.27.4; fixed in 1.26.11, 1.27.4

## Suggested inspection (read-only)
- Go toolchain: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on toolchain.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6857 (OSV record GO-2026-6857 lists affected ranges: Go toolchain >=0 =1.27.0-0 <1.27.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…