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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** ALPINE-CVE-2026-97034, DEBIAN-CVE-2026-97034, GHSA-775q-r7gv-cr2x, GO-2026-6857, UBUNTU-CVE-2026-97034

## What is CVE-2026-97034?

CVE-2026-97034 is a vulnerability in cmd/go, published on 11 Nov 2026. 

### Official 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.

## Which versions are affected by CVE-2026-97034?

1 open source package ship an affected version, including toolchain.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `toolchain` | Go | All versions | 1.26.11, 1.27.4 |

## How do I fix CVE-2026-97034?

Upgrade toolchain to a fixed version for your release line: 1.26.11 or 1.27.4.

## Is CVE-2026-97034 being exploited?

There is no known exploitation of CVE-2026-97034 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97034 and fix it if it is affected.

What it is: CVE-2026-97034 is a vulnerability in cmd/go, published on 11 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-97034 in the wild and no public exploit code.

Affected packages and fixed versions:
- toolchain (Go): affected all versions; fixed in 1.26.11, 1.27.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97034/ (Markdown: https://insights.sbomify.com/CVE-2026-97034/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97034
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97034
- OSV: https://osv.dev/vulnerability/CVE-2026-97034

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97034/
Summaries are generated and may contain mistakes; the official description above is the record.