Go will refuse certificate chains through a set of distrusted intermediates

What changed

The Go issue was opened on 19 October and closed with a fix on 20 October. Go's certificate verification will drop chains that contain a small set of intermediates, citing "specific security concerns around their operation". The title mentions eight SPKIs; the page does not name them. Backports were opened for 1.26 and 1.27, and downstream projects referred to upgrading to Go 1.27.3.

A maintainer said the team learned of the problem the Monday before and kept the notes vague to limit attackers' head start.

The vague notes hide a full key compromise, and Go is not alone

Readers guessed at a mundane policy dispute until the founder of SSLMate, a certificate-tooling company explained what the logs showed:

"two Certificate Transparency log implementations were updated to block the logging of certificates issued by the CAs. This likely indicates total private key compromise… it also means there will be no place to record forged certificates found in the wild."

The same commenter listed Node, rustls/webpki and Electron as shipping equivalent blocks and called the upgrade "very serious". That answers the question of why a language runtime is doing this at all; a commenter answering the complaint that Go ships its own root list put it plainly:

"This is an additional, ad-hoc blocklist for compromised intermediaries, it's not even roots. The roots are just taken from your system."

Because the blocklist lives in the Go release rather than the OS trust store, an OS-level update will not protect a statically built Go binary: it has to be rebuilt on the patched toolchain.