Advisory

GO-2026-6851

Also known as: CVE-2026-97040

Summary

Cgo directive injection via .syso files disguised as Go object files in cmd/go and cmd/link

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-11-11 02:51 UTC
Modified
2026-11-11 03:15 UTC

Affected packages and fixes

toolchain

Go · All systems

Affected

  • introduced 0, fixed 1.26.11, introduced 1.27.0-0, fixed 1.27.4 (semver)

Fixed versions

1.26.11, 1.27.4

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Go Vulnerability Database · CC BY 4.0

Sources & licences