Golang Go any version

Stack exhaustion when reading certain archives in compress/gzip

Excessive memory allocation in net/http and net/textproto

Stack exhaustion when decoding certain messages in encoding/gob

Path traversal on Windows in path/filepath

Unbounded memory consumption when reading headers in archive/tar

Certificate.Verify in crypto/x509 in Go 1.18.x before 1.18.1 can be caused to panic on macOS when presented with certain malformed certificates. This allows a remote TLS server to cause a TLS client to panic.

Excessive resource consumption in net/http, net/textproto and mime/multipart

Memory exhaustion when compiling regular expressions in regexp/syntax

Infinite loop in parsing in go/scanner

Panic when processing post-handshake message on QUIC connections in crypto/tls

Memory exhaustion in QUIC connection handling in crypto/tls

On Darwin, user's trust preferences for root certificates were not honored. If the user had a root certificate loaded in their Keychain that was explicitly not trusted, a Go program would still verify a connection using that root certificate.

Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel

Excessive resource consumption in mime/multipart

Restricted file access on Windows in os and net/http

Incorrect sanitization of forwarded query parameters in net/http/httputil

Command 'go get' may unexpectedly fallback to insecure git in cmd/go

Panic on large handshake records in crypto/tls

Crash when handling long CNAME response in net

Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

Quadratic string concatentation in consumeComment in net/mail

Unsanitized NUL in environment variables on Windows in syscall and os/exec

Incorrect parsing of IPv6 host literals in net/url

Quadratic string concatenation in consumePhrase in net/mail

Unexpected work during chain building in crypto/x509

Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls

Panic in Dial and LookupPort when handling NUL byte on Windows in net

Quadratic complexity when parsing some invalid inputs in encoding/pem

Excessive resource consumption when printing error string for host certificate validation in crypto/x509

pkg/suci/suci.go in free5GC udm before 1.2.0, when Go before 1.19 is used, allows an Invalid Curve Attack because it may compute a shared secret via an uncompressed public key that has not been validated. An attacker can send arbitrary SUCIs to the UDM, which tries to decrypt them via both its private key and the attacker's public key.

Quadratic complexity when checking name constraints in crypto/x509

Inefficient policy validation in crypto/x509

Panic when validating certificates with DSA public keys in crypto/x509

Malicious module proxy can bypass checksum database in cmd/go

Improper sanitization of CSS values in html/template

Improper handling of empty HTML attributes in html/template

Miscompilation allows memory corruption via CONVNOP-wrapped array copy in cmd/compile

Incorrect results returned from Rows.Scan in database/sql

Unexpected code execution when invoking toolchain in cmd/go

The crypto/tls package of Go through 1.16.5 does not properly assert that the type of public key in an X.509 certificate matches the expected type when doing a RSA based key exchange, allowing a malicious TLS server to cause a TLS client to panic.