AZL-113450: CVE-2026-97033 affecting package golang 1.26.11-1

Published Nov 11, 2026
·
Updated

Building a malicious package that uses cgo could cause arbitrary code execution at build time through several compiler and linker flags permitted in "#cgo" directives. Specifically, "--sysroot" in GCC and Clang relocates compiler subprograms, spec files, and CRT startup objects to an attacker-controlled directory; "-target" in Clang falls back to executing target helper tools from the current working directory when not found in PATH; "-isysroot" and "-Wl,-syslibroot" can pass a regular file on disk to GNU ld.bfd, which interprets it as a positional linker script; and "-x" permitted specifying arbitrary compiler input languages beyond those supported by cgo. "--sysroot" and "-target" are now disallowed in "#cgo" flags, "-isysroot" and "-Wl,-syslibroot" are verified not to point to regular files, and "-x" is restricted to the C, C++, Objective-C, and assembler languages supported by cgo.

Affected Software

1 affected component
azure-linux/golang<=1.26.11-1

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 exposed to this issue?

Build environments that compile untrusted or malicious Go packages using cgo are exposed. The described impact occurs during the build process, so systems that only run already-built binaries are not identified as affected by the provided information.

2

What does an attacker need to exploit it?

An attacker needs to cause a malicious package containing cgo directives to be built. The package can use permitted #cgo compiler or linker flags to trigger code execution during compilation or linking.

3

Are the risky cgo flags still permitted?

The remediation disallows --sysroot and -target in #cgo flags. It also validates that -isysroot and -Wl,-syslibroot do not reference regular files, and limits -x to C, C++, Objective-C, and assembler languages supported by cgo.

4

What should be done if patching cannot happen immediately?

Do not build untrusted packages that use cgo in the affected environment. Treat build workers compiling third-party source as potentially exposed until the described cgo flag restrictions are in place.

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