RHSA-2026:49944

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation.

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…

When adding a key to a remote agent constraint extensions such as [email protected] were not serialized in the request.

A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop.

The net/url package does not set a limit on the number of query parameters in a query.

Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards.

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.

During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service.

url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.

The RSA and DSA public key parsers did not enforce size limits on key parameters.

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.

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out.

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened.