Go toolchain · Go · published 2026-11-11
CVE-2026-97039Flag sanitization bypass via "#cgo pkg-config:" directives in cmd/go
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-97039 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 33% of all CVEs. This Go vulnerability: CVSS 8.3 (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.4% (33th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L | 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 pkg-config:" directives could load untrusted pkg-config ".pc" files or inject unvalidated compiler and linker flags. The pkg-config flag allowlist previously permitted "--with-path=" and "--personality=", allowed "--define-variable=" values beginning with "=" or "$" (which can rewrite paths in system ".pc" files into sysroot-prefixed "-L=" or "-L$SYSROOT" linker search paths), and allowed package arguments ending in ".pc" or containing path separators or "..", which caused pkg-config to load local ".pc" files directly from the package directory. In addition, flags returned by "pkg-config --cflags" in cgoCPPFLAGS were not checked when determining whether internal linking is safe. The go command now disallows "--with-path=", "--personality=", leading "=" or "$" characters in "--define-variable=" values, and local ".pc" paths in "#cgo pkg-config:" directives, and inspects cgoCPPFLAGS when checking internal linking compatibility.
Quoted from the CVE Program record.