AZL-113654: CVE-2026-97041 affecting package tensorflow 2.16.1-11

Published Nov 11, 2026
·
Updated

Building a malicious package containing "//go:cgo" compiler directives could inject arbitrary flags into the external linker invocation on ELF platforms. The compiler and linker did not reject commas in "//go:cgoimportdynamic", "//go:cgoexportdynamic", "//go:cgoexportstatic", "//go:cgoimportstatic", and "//go:cgodynamiclinker" directives, and the linker passed the dynamic linker path using "-Wl,--dynamic-linker,<path>". Furthermore, the two-argument form of "//go:cgoimportdynamic" (which is permitted in non-cgo Go source files) could overwrite the external symbol name of a symbol already marked for cgo export. A symbol name or dynamic linker path containing a comma or leading "@" could split "-Wl,--export-dynamic-symbol=" or "-Wl,--dynamic-linker," into arbitrary host linker flags or response file arguments. The compiler and linker now reject commas in "//go:cgo" symbol and dynamic linker directives, the linker passes "-Wl,--dynamic-linker=<path>", and "cgoimportdynamic" no longer overwrites symbols exported via "cgoexportdynamic" or "cgoexportstatic".

Affected Software

1 affected component
azure-linux/tensorflow<=2.16.1-11

Event History

Nov 11, 2026
Advisory Published
via OSV·05:19 AM
Data Sourced
via OSV·05:19 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Who is realistically exposed to exploitation?

Build environments on ELF platforms that compile a malicious package containing the affected //go:cgo_* directives are exposed. The issue targets the compiler-to-external-linker invocation during package building.

2

What does an attacker need to control?

An attacker needs to supply or cause the build of a malicious package using affected //go:cgo_* directives. Commas or a leading "@" in specified symbol names or a dynamic linker path can be used to inject host linker flags or response-file arguments.

3

Are non-cgo Go source files relevant?

Yes. The two-argument form of //go:cgo_import_dynamic is permitted in non-cgo Go source files and could overwrite the external symbol name of a symbol already marked for cgo export.

4

How can teams identify suspicious source before building it?

Review package source for //go:cgo_import_dynamic, //go:cgo_export_dynamic, //go:cgo_export_static, //go:cgo_import_static, and //go:cgo_dynamic_linker directives. Treat commas in directive symbol names or dynamic-linker paths, and leading "@" values where they reach linker arguments, as suspicious.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203