# CVE-2026-97034: Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Go toolchain / cmd/go (cmd/go): ≥ 0; < 1.26.11 (affected, semver); ≥ 1.27.0-0; < 1.27.4 (affected, semver). Source: CNA: Go

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-77

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://go.dev/cl/862147 (CNA: Go)

- https://go.dev/issue/82576 (CNA: Go)

- https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM (CNA: Go)

- https://pkg.go.dev/vuln/GO-2026-6857 (CNA: Go)

## Provenance

- CNA: Go: https://www.cve.org/CVERecord?id=CVE-2026-97034; retrieved 2026-11-11; source updated 2026-11-11

Revision: deac31f539e2c5f0232af7b8dd9e8967c94cdff99d5c4c2feef51864d6f6584f

Canonical: https://y2.dev/cve/CVE-2026-97034

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.