Go toolchain · Go · published 2026-11-11

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

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-97040 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 51% of all CVEs. This Go vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Fixed upstream in Go 1.27.4, 1.26.11; Ubuntu still has unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.27.4, 1.26.11.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixiegolang-1.24Won’t fix
12 bookwormgolang-1.19Won’t fix
Ubuntu (+28 more packages)26.04 LTSgolang-1.24No fix yet
24.04 LTSgolang-1.24No fix yet
22.04 LTSgolang-1.24No fix yet

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.27.4, 1.26.11

    Upgrade to 1.27.41.26.11

    Why: Vendor security release for server software (most severe: CVE-2026-97040).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (51th pct)FIRST EPSS v2026.06.15
CVSS base score9.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →