cve.bz

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

no score yetEPSS 0.2%Fix available

go toolchain: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in toolchain 1.26.11, 1.27.4.

On this page
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.
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
Assigned by
Go (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-97040 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97040?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97040?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97040 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-97040

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-97040](https://cve.bz/cve/badge/CVE-2026-97040.svg)](https://cve.bz/cve/CVE-2026-97040)

HTML:

<a href="https://cve.bz/cve/CVE-2026-97040"><img src="https://cve.bz/cve/badge/CVE-2026-97040.svg" alt="CVE-2026-97040"></a>

Affected

  • go toolchain:cmd/go
  • go toolchain:cmd/link

Versions

From the CNA's record in the CVE List.

ProductAffected
Go toolchain cmd/gobefore 1.26.11
Go toolchain cmd/gofrom 1.27.0-0 before 1.27.4
Go toolchain cmd/linkbefore 1.26.11
Go toolchain cmd/linkfrom 1.27.0-0 before 1.27.4

Fix and patched versions

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GO-2026-6851Gotoolchain<1.26.11
>=1.27.0-0 <1.27.4
1.26.11, 1.27.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12golang-1.19no fix listedDEBIAN-CVE-2026-97040
Debian13golang-1.24no fix listedDEBIAN-CVE-2026-97040
Debian14golang-1.261.26.11-1DEBIAN-CVE-2026-97040
Debian14golang-1.271.27.4-1DEBIAN-CVE-2026-97040
Ubuntu14.04:LTSgolang-1.10no fix listedUBUNTU-CVE-2026-97040
Ubuntu16.04:LTSgolang-1.6, golang-1.10no fix listedUBUNTU-CVE-2026-97040
Ubuntu18.04:LTSgolang-1.8, golang-1.9, golang-1.10no fix listedUBUNTU-CVE-2026-97040
Ubuntu20.04:LTSgolang-1.13, golang-1.14, golang-1.18 and 3 moreno fix listedUBUNTU-CVE-2026-97040
Ubuntu22.04:LTSgolang-1.17, golang-1.18, golang-1.20 and 6 moreno fix listedUBUNTU-CVE-2026-97040
Ubuntu24.04:LTSgolang-1.21, golang-1.22, golang-1.23 and 3 moreno fix listedUBUNTU-CVE-2026-97040
Ubuntu26.04:LTSgolang-1.23, golang-1.24, golang-1.25 and 1 moreno fix listedUBUNTU-CVE-2026-97040
Ubuntu26.10golang-1.26, golang-1.27no fix listedUBUNTU-CVE-2026-97040
UbuntuPro:16.04:LTSgolang-1.13, golang-1.18no fix listedUBUNTU-CVE-2026-97040
UbuntuPro:18.04:LTSgolang-1.13, golang-1.16, golang-1.18no fix listedUBUNTU-CVE-2026-97040
UbuntuPro:20.04:LTSgolang-1.16no fix listedUBUNTU-CVE-2026-97040
UbuntuPro:22.04:LTSgolang-1.13no fix listedUBUNTU-CVE-2026-97040
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morego1.261.26.11-150000.1.39.1SUSE-SU-2026:5227-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morego1.271.27.4-150000.1.18.1SUSE-SU-2026:5226-1
openSUSETumbleweedgo1.261.26.11-1.1openSUSE-SU-2026:12529-1
Alpinev3.24go1.26.11-r0ALPINE-CVE-2026-97040
Azure Linux3gccno fix listedAZL-113414
Azure Linux3golangno fix listedAZL-113441 AZL-113477
Azure Linux3python-tensorboardno fix listedAZL-113576
Azure Linux3tensorflowno fix listedAZL-113645

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

References

Check your stackJSON