AZL-113675: CVE-2026-97035 affecting package tensorflow 2.16.1-11
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
Event History
Frequently Asked Questions
Who is exposed to this issue?
Build environments using Clang or GCC are exposed when they build a malicious package that uses cgo. The issue is triggered through compiler or linker flags supplied in #cgo directives.
What does an attacker need to exploit it?
An attacker needs a malicious cgo-using package to be built in the affected environment. The package must use the previously allowlisted -gen-* or -gnat* flag patterns in #cgo compiler or linker flags.
What could successful exploitation allow?
It could cause unexpected code execution during the build or write compilation-database fragments and sidecar output files to arbitrary directories. It may also cause subsequent arguments to reach the linker as unvalidated positional inputs.