Skip to main content
CVE-2026-97039VulnerabilityPublished

Building a malicious package that uses "#cgo pkg-config:" directives could load untrusted pkg-config ".pc" files or

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97039· High

Not known to be exploited : upgrade to 1.27.4 or 1.26.11 soon.

Data as of 11 Nov 2026, 08:05 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 1.27.4, 1.26.11

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade cmd/go to 1.27.4 or 1.26.11.

Affected software

ProductAffectedFixed in
Go toolchaincmd/goAffected
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.27.4
Go toolchaincmd/goAffected
  • <1.26.11
Fixed in
  • 1.26.11
Gocmd/gopkg:golang/cmd/goOther threatsAffected
  • <1.26.11
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.26.11
  • 1.27.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The Go command has been updated to disallow the problematic pkg-config flags and local ".pc" file paths in "#cgo pkg-config:" directives and to inspect cgoCPPFLAGS for internal linking safety. Users should update to the fixed Go version once available.

Description

A vulnerability exists in the handling of "#cgo pkg-config:" directives in Go packages, where malicious packages could load untrusted pkg-config ".pc" files or inject unvalidated compiler and linker flags. This occurs due to insufficient restrictions on certain pkg-config flags and local ".pc" file paths, potentially allowing manipulation of build configurations. The Go command has been updated to disallow problematic flags and local ".pc" paths and to inspect flags for safer internal linking.

References

Community reviews

Loading reviews…