DHI-wann-doqv-7rav-yxhi

Source
https://scout.docker.com/v/DHI-wann-doqv-7rav-yxhi
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-wann-doqv-7rav-yxhi.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-wann-doqv-7rav-yxhi
Upstream
  • CVE-2026-97040
Published
2026-11-18T19:52:05Z
Modified
2026-11-18T20:03:33Z
Severity
  • 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
Building a package containing a crafted ".syso" file could bypass cgo flag validation and inject arbitrary linker flags…
Details

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.

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-wann-doqv-7rav-yxhi.json"