CVE-2026-97040 Affecting go package, versions <1.26.11-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.25% (16th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALPINE324-GO-22526260
  • published13 Nov 2026
  • disclosed11 Nov 2026

Introduced: 11 Nov 2026

NewCVE-2026-97040  (opens in a new tab)

How to fix?

Upgrade Alpine:3.24 go to version 1.26.11-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream go package and not the go package as distributed by Alpine. See How to fix? for Alpine:3.24 relevant fixed versions and status.

Building a package containing a crafted ".syso" file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading ".syso" entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A ".syso" file beginning with a "go object" header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as "cgo_ldflag" or "cgo_dynamic_linker") embedded in the ".syso" file to be passed to the external linker without validation. Additionally, ".syso" filenames longer than 16 bytes lost their ".syso" extension when truncated in archive headers, and unrecognized ".syso" formats forced external linking in pure-Go builds. The linker now rejects ".syso" files that are not recognized host object formats, and "cmd/go" and "cmd/pack" preserve the ".syso" suffix when truncating long archive member names.

CVSS Base Scores

version 3.1