ALPINE-CVE-2026-97035: Alpine/go vulnerability
When using Clang or GCC, building a malicious package that uses cgo could cause unexpected code execution at build time or write files to arbitrary directories via "-gen-" or "-gnat" flags in "#cgo" directives. The "-g" wildcard in the compiler and linker flag allowlists previously matched Clang's two-argument "-gen-cdb-fragment-path <dir>" flag and GCC's two-argument "-gnatO <file>" flag, permitting compilation database fragments and sidecar output files to be written to arbitrary directories and desynchronizing flag argument parsing between the go command and the compiler driver so that subsequent arguments could be passed as unvalidated positional inputs to the linker. "-gen-" and "-gnat" flags are now disallowed in "#cgo" compiler and linker flags.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/goto a version that resolves this vulnerability.Fixed in 1.26.11-r0
Event History
Frequently Asked Questions
Who is exposed to this issue?
Build environments using Alpine's Go toolchain with Clang or GCC are exposed when they build an untrusted or malicious package that uses cgo. The issue occurs during package build time.
What does an attacker need to exploit it?
An attacker needs to cause a target to build a malicious cgo-enabled package containing crafted #cgo compiler or linker directives. The directives can use the affected -gen-* or -gnat* flag patterns.
What could exploitation allow?
Exploitation could cause unexpected code execution during the build. It could also write compilation-database fragments or sidecar output files to arbitrary directories and pass subsequent arguments to the linker as unvalidated positional inputs.
What mitigation is described?
The affected -gen-* and -gnat* flags are now disallowed in #cgo compiler and linker flags. Until that change is present, avoid building untrusted cgo packages with Clang or GCC.