gRPC-Go has an authorization bypass via missing leading slash in :path
gRPC-Go is the Go language implementation of gRPC.
Logging for Red Hat OpenShift - 6.2.12
Released 2026-07-29 · Red Hat rating Important · View on Red Hat →
gRPC-Go is the Go language implementation of gRPC.
The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label.
When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different case than the constraint.
Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.
Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC 5322.
Prometheus is an open-source monitoring system and time series database.
Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.
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.
When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.
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.
Prometheus is an open-source monitoring system and time series database.
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.
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.
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree.
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree.