CVE-2026-97040
Description
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.
AI Remediation Playbook Pro+
Get step-by-step remediation playbooks with specific commands, verification steps, and rollback procedures.
Upgrade to Pro+AI Attack Path AnalysisPro+
Visualize potential attack chains and lateral movement paths with AI-powered analysis.
AI Risk ForecastingPro+
Predict exploitation likelihood with AI-powered threat intelligence forecasting.
AI Compliance MappingPro+
Map vulnerabilities to compliance frameworks with AI-assisted gap analysis.
Weakness Types (CWE)
MITRE ATT&CK TechniquesThreat Intelligence
How attackers may exploit this vulnerability