Go toolchain · Go · published 2026-11-11
CVE-2026-97033Unexpected code execution via --sysroot, -target, -isysroot, -Wl,-syslibroot, and -x cgo flags in cmd/go
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-97033 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 46% of all CVEs. This Go vulnerability: CVSS 8.8 (v3.1), 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.
Jump to: Remediation Exploit intelAffected versionsDescription
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.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | golang-1.24 | Won’t fix |
| 12 bookworm | golang-1.19 | Won’t fix | |
| Ubuntu (+28 more packages) | 26.04 LTS | golang-1.24 | No fix yet |
| 24.04 LTS | golang-1.24 | No fix yet | |
| 22.04 LTS | golang-1.24 | No 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
Language runtimeGo
Go security releases: 1.27.4, 1.26.11
Upgrade to
1.27.41.26.11Why: Vendor security release for server software (most severe: CVE-2026-97040).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (46th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Go toolchain cmd/go
0to before1.26.11(affected)1.27.0-0to before1.27.4(affected)
Description (from the CVE record)#
Building a malicious package that uses cgo could cause arbitrary code execution at build time through several compiler and linker flags permitted in "#cgo" directives. Specifically, "--sysroot" in GCC and Clang relocates compiler subprograms, spec files, and CRT startup objects to an attacker-controlled directory; "-target" in Clang falls back to executing target helper tools from the current working directory when not found in PATH; "-isysroot" and "-Wl,-syslibroot" can pass a regular file on disk to GNU ld.bfd, which interprets it as a positional linker script; and "-x" permitted specifying arbitrary compiler input languages beyond those supported by cgo. "--sysroot" and "-target" are now disallowed in "#cgo" flags, "-isysroot" and "-Wl,-syslibroot" are verified not to point to regular files, and "-x" is restricted to the C, C++, Objective-C, and assembler languages supported by cgo.
Quoted from the CVE Program record.