DHI-txpy-qbqh-pigy-g5u7

Source
https://scout.docker.com/v/DHI-txpy-qbqh-pigy-g5u7
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-txpy-qbqh-pigy-g5u7.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-txpy-qbqh-pigy-g5u7
Upstream
  • CVE-2026-97034
Published
2026-11-18T19:52:05Z
Modified
2026-11-18T20:03:27Z
Severity
  • 8.8 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H CVSS Calculator
Summary
When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via…
Details

When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files ("specs" or ".spec"). When linking with "-fopenmp", "-fopenacc", or "-fsanitize=" in "#cgo LDFLAGS", GCC's built-in link spec evaluates "%:include(libgomp.spec)" or "%:include(libsanitizer.spec)" and searches for spec files in "-L" and sysroot directories (including subdirectories and multilib sibling directories such as "../lib64"), as well as the working directory when "-fopenmp" or "-fopenacc" is used or when "-fsanitize=" is combined with "-static" or "-static-lib". The go command now rejects "-L", "-isysroot", and "-Wl,-syslibroot" directories (and the working and package directories when applicable) that contain GCC spec files, and disallows "@" and "-" prefixes in "-fsanitize=" compiler flag values.

References

Affected packages

Docker Hardened Images:Alpine:3.24 / go

Package

Name
go
Purl
pkg:apk/dhi/go

Affected ranges

Affected versions

1.*
1.26.4-r0
1.26.5-r0
1.27.0-r0
1.27.1-r0
1.27.2-r0
1.27.3-r0
1.27.4-r0

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-txpy-qbqh-pigy-g5u7.json"