Is CVE-2026-97038 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-97038 being exploited in the wild.

How severe is CVE-2026-97038?

Informational severity, published 11 November 2026.

Which products and versions are affected?

go (Go) versions prior to the 2026-11-11 fix; toolchain (Go) SEMVER:introduced=0,fixed=1.26.11,introduced=1.27.0-0,fixed=1.27.4.

Is there a fix for CVE-2026-97038?

Yes. toolchain (Go): upgrade to 1.27.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-97038 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-97038?

Check whether you run go (Go) or toolchain (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-97038: Go linker code injection via malicious package compilation

CVE-2026-97038 · Severity: info · Published 2026-11-11

Go's build system can be exploited when compiling packages containing malicious ".syso" files or cgo linker inputs, allowing attackers to inject arbitrary linker flags or execute code during the link phase. When a developer builds a Go package from untrusted sources, the malicious inputs could alter the final binary or run arbitrary commands on their build system.

Technologies: go (Go), toolchain (Go). Vendors: Go.

Quick answers

Is CVE-2026-97038 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-97038 being exploited in the wild.
How severe is CVE-2026-97038?: Informational severity, published 11 November 2026.
Which products and versions are affected?: go (Go) versions prior to the 2026-11-11 fix; toolchain (Go) SEMVER:introduced=0,fixed=1.26.11,introduced=1.27.0-0,fixed=1.27.4.
Is there a fix for CVE-2026-97038?: Yes. toolchain (Go): upgrade to 1.27.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-97038 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-97038?: Check whether you run go (Go) or toolchain (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

toolchain (Go): upgrade to 1.27.4 or later
```
go get toolchain@v1.27.4
```

Technical details

The vulnerability exists in Go's handling of linker inputs, which did not validate ".syso" files or entries in "#cgo LDFLAGS" for embedded malicious directives. Attackers could disguise GNU ld linker scripts as libraries, inject flags via PE/COFF ".drectve" sections (Windows) or Mach-O "LC_LINKER_OPTION" commands (macOS), or invoke LTO plugins through ELF/PE/Mach-O intermediate representation sections. The fix adds validation to reject unallowlisted directives and disallows suspicious linker flag syntax.

Affected products

Go Go versions prior to the 2026-11-11 fix

Identifiers

CVE-2026-97038
GO-2026-6853

Timeline

2026-11-11: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.