THREATIST.IORead the docs Red Hat Hardened Images RPMs bug fix and enhancement update
Released 2026-04-10 · Red Hat rating Important · View on Red Hat →
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have…
Arithmetic over induction variables in loops were not correctly checked for underflow or overflow.
The net/url package does not set a limit on the number of query parameters in a query.
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources.
Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic
url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
A discrepancy between how Go and C/C++ comments were parsed allowed for code smuggling into the resulting cgo binary.
The ParseAddress function constructs domain-literal address components through repeated string concatenation.
gopls by default communicates via pipe.
Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.
Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service.
Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.
Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.
Building a malicious file with cmd/go can cause can cause a write to an attacker-controlled file with partial control of the file content.
An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate.
The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.
Downloading and building modules with malicious version strings can cause local code execution.
Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out.
The compiler is meant to unwrap pointers which are the operands of a memory move; a no-op interface conversion prevented the compiler from making the correct determination about non-overlapping moves, potentially leading…
The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines.
The html.Parse function in golang.org/x/net/html has an infinite parsing loop when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.
Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit.
Parsing a maliciously crafted DER payload could allocate large amounts of memory, causing memory exhaustion.
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.
The html.Parse function in golang.org/x/net/html has quadratic parsing complexity when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.
A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.
On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chmod can operate on the target of the symlink, even when the target lies outside the root.
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed befo…
archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened.
When Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols sent by the client) which is not escaped.
Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used.
tar.Reader can allocate an unbounded amount of memory when reading a maliciously-crafted archive containing a large number of sparse regions encoded in the "old GNU sparse map" format.
The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL.
When using http.CrossOriginProtection, the AddInsecureBypassPattern method can unexpectedly bypass more requests than intended.
tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files.
It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../".
On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root in which the File was opened.