rpm package
opensuse/go1.26&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/go1.26&distro=openSUSE%20Tumbleweed
Vulnerabilities (68)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-97054 | Med | 5.9 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or Max | |
| CVE-2026-97043 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | Building a malicious package that uses cgo could bypass "#cgo LDFLAGS" validation and cause unexpected code execution at build time, or cause the go command to panic, via crafted quoting in "//go:cgo_ldflag" directives. When "cmd/cgo" generates "_cgo_gotypes.go", it quotes each " | |
| CVE-2026-97042 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | Building a malicious package that uses "//go:cgo_import_dynamic" or links against a crafted PE object on Windows could pass unsafe library arguments to the external linker. The compiler only checked the first character of the library name in "//go:cgo_import_dynamic" directives a | |
| CVE-2026-97041 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | Building a malicious package containing "//go:cgo_*" compiler directives could inject arbitrary flags into the external linker invocation on ELF platforms. The compiler and linker did not reject commas in "//go:cgo_import_dynamic", "//go:cgo_export_dynamic", "//go:cgo_export_stat | |
| CVE-2026-97040 | Cri | 9.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | 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) befor | |
| CVE-2026-97039 | Hig | 8.3 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | 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=" v | |
| CVE-2026-97038 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including ".syso" files, direct object or library inputs in "#cgo LDFLAGS", and libraries in "-L" directories— | |
| CVE-2026-97037 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via "#cgo LDFLAGS". Split "-Wl," flags that consume a following argument (such as "-Wl,-rpath", "-Wl,--just-symbols", and "-Wl,-undefined | |
| CVE-2026-97036 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | On Darwin, building a malicious package that uses cgo could cause arbitrary code execution when using the Apple linker due to passing "-l to_library " in a "#cgo LDFLAGS" directive. The Apple linker recombines the separated arguments "-l" and "to_library" into "-lto_library | |
| CVE-2026-97035 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | When using Clang or GCC, building a malicious package that uses cgo could cause unexpected code execution at build time or write files to arbitrary directories via "-gen-*" or "-gnat*" flags in "#cgo" directives. The "-g*" wildcard in the compiler and linker flag allowlists previ | |
| CVE-2026-97034 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | 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 "% | |
| CVE-2026-97033 | Hig | 8.8 | < 1.26.11-1.1 | 1.26.11-1.1 | Nov 11, 2026 | 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 t | |
| CVE-2026-111943 | Med | 6.8 | < 1.26.10-1.1 | 1.26.10-1.1 | Oct 21, 2026 | On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return a | |
| CVE-2026-97032 | Hig | 7.5 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to | |
| CVE-2026-97031 | Hig | 7.5 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory ampli | |
| CVE-2026-97030 | Med | 6.1 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped. | |
| CVE-2026-94448 | Med | 6.1 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression lit | |
| CVE-2026-94447 | Hig | 7.8 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain always goes to the network fo | |
| CVE-2026-94444 | Hig | 7.8 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips14 | |
| CVE-2026-94440 | Hig | 7.5 | < 1.26.9-1.1 | 1.26.9-1.1 | Oct 8, 2026 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. |
- affected < 1.26.11-1.1fixed 1.26.11-1.1
For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or Max
- affected < 1.26.11-1.1fixed 1.26.11-1.1
Building a malicious package that uses cgo could bypass "#cgo LDFLAGS" validation and cause unexpected code execution at build time, or cause the go command to panic, via crafted quoting in "//go:cgo_ldflag" directives. When "cmd/cgo" generates "_cgo_gotypes.go", it quotes each "
- affected < 1.26.11-1.1fixed 1.26.11-1.1
Building a malicious package that uses "//go:cgo_import_dynamic" or links against a crafted PE object on Windows could pass unsafe library arguments to the external linker. The compiler only checked the first character of the library name in "//go:cgo_import_dynamic" directives a
- affected < 1.26.11-1.1fixed 1.26.11-1.1
Building a malicious package containing "//go:cgo_*" compiler directives could inject arbitrary flags into the external linker invocation on ELF platforms. The compiler and linker did not reject commas in "//go:cgo_import_dynamic", "//go:cgo_export_dynamic", "//go:cgo_export_stat
- affected < 1.26.11-1.1fixed 1.26.11-1.1
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) befor
- affected < 1.26.11-1.1fixed 1.26.11-1.1
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=" v
- affected < 1.26.11-1.1fixed 1.26.11-1.1
Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including ".syso" files, direct object or library inputs in "#cgo LDFLAGS", and libraries in "-L" directories—
- affected < 1.26.11-1.1fixed 1.26.11-1.1
Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via "#cgo LDFLAGS". Split "-Wl," flags that consume a following argument (such as "-Wl,-rpath", "-Wl,--just-symbols", and "-Wl,-undefined
- affected < 1.26.11-1.1fixed 1.26.11-1.1
On Darwin, building a malicious package that uses cgo could cause arbitrary code execution when using the Apple linker due to passing "-l to_library " in a "#cgo LDFLAGS" directive. The Apple linker recombines the separated arguments "-l" and "to_library" into "-lto_library
- affected < 1.26.11-1.1fixed 1.26.11-1.1
When using Clang or GCC, building a malicious package that uses cgo could cause unexpected code execution at build time or write files to arbitrary directories via "-gen-*" or "-gnat*" flags in "#cgo" directives. The "-g*" wildcard in the compiler and linker flag allowlists previ
- affected < 1.26.11-1.1fixed 1.26.11-1.1
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 "%
- affected < 1.26.11-1.1fixed 1.26.11-1.1
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 t
- affected < 1.26.10-1.1fixed 1.26.10-1.1
On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return a
- affected < 1.26.9-1.1fixed 1.26.9-1.1
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to
- affected < 1.26.9-1.1fixed 1.26.9-1.1
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory ampli
- affected < 1.26.9-1.1fixed 1.26.9-1.1
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
- affected < 1.26.9-1.1fixed 1.26.9-1.1
When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression lit
- affected < 1.26.9-1.1fixed 1.26.9-1.1
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain always goes to the network fo
- affected < 1.26.9-1.1fixed 1.26.9-1.1
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips14
- affected < 1.26.9-1.1fixed 1.26.9-1.1
Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.
Page 1 of 4