rpm package
almalinux/golang-bin
pkg:rpm/almalinux/golang-bin
Vulnerabilities (111)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-111943 | Med | 6.8 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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.10-1.el9_8 | 1.26.10-1.el9_8 | 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. | |
| CVE-2026-94439 | Hig | 7.5 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tun | |
| CVE-2026-78669 | Hig | 7.5 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. | |
| CVE-2026-78667 | Hig | 7.5 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU. | |
| CVE-2026-78663 | Cri | 9.1 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to | |
| CVE-2026-78660 | Hig | 7.5 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client | |
| CVE-2026-78659 | Hig | 7.5 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit | |
| CVE-2026-56866 | Hig | 7.5 | < 1.26.10-1.el9_8 | 1.26.10-1.el9_8 | Oct 8, 2026 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connecti | |
| CVE-2026-56862 | Hig | 7.5 | < 1.26.7-1.el9_8 | 1.26.7-1.el9_8 | Aug 13, 2026 | Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indef | |
| CVE-2026-56860 | Med | 5.9 | < 1.26.7-1.el9_8 | 1.26.7-1.el9_8 | Aug 13, 2026 | Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-b | |
| CVE-2026-56859 | Hig | 7.5 | < 1.26.7-1.el9_8 | 1.26.7-1.el9_8 | Aug 13, 2026 | Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion. | |
| CVE-2026-56858 | Med | 6.1 | < 1.26.7-1.el9_8 | 1.26.7-1.el9_8 | Aug 13, 2026 | Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS. | |
| CVE-2026-56853 | Hig | 7.5 | < 1.26.7-1.el9_8 | 1.26.7-1.el9_8 | Aug 13, 2026 | When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this. |
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
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.10-1.el9_8fixed 1.26.10-1.el9_8
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tun
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit
- affected < 1.26.10-1.el9_8fixed 1.26.10-1.el9_8
When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connecti
- affected < 1.26.7-1.el9_8fixed 1.26.7-1.el9_8
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indef
- affected < 1.26.7-1.el9_8fixed 1.26.7-1.el9_8
Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-b
- affected < 1.26.7-1.el9_8fixed 1.26.7-1.el9_8
Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.
- affected < 1.26.7-1.el9_8fixed 1.26.7-1.el9_8
Previously, pathological inputs could close an unescaped '/' early, allowing for attack-controlled data to inject arbitrary content, potentially leading to XSS.
- affected < 1.26.7-1.el9_8fixed 1.26.7-1.el9_8
When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.
Page 1 of 6