The Go Security team issued its first-ever URGENT track security release on October 19, 2026, to safeguard Go users and their applications against a critical compromise within a public key infrastructure (PKI) involving certificates from eMudhra.
This targeted patch was deployed within approximately seven and a half hours following notification of the compromise. The incident stemmed from earlier actions on October 17, when Mozilla added eight intermediate certificates, six for TLS and two for code signing, issued by an eMudhra-controlled root certificate to OneCRL, thereby blocking their use in Firefox.
Security researchers subsequently investigated this action. On October 19, the Go Security team learned of these investigations, which revealed that the keys for these intermediates were trivially weak, enabling private key recovery in microseconds.
Because the eMudhra root certificate was present in most trusted root programs, private key recovery would permit any attacker to sign arbitrary TLS certificates for any domain. This capability would allow an attacker to impersonate any TLS server a targeted machine attempted to connect to via man-in-the-middle (MITM) TLS connections.
Go's standard library includes a TLS certificate verifier utilized when applications use net/http or crypto/tls to connect to a TLS service. While Windows and macOS delegate these checks to platform APIs, Go uses its own verifier implementation on Linux, which lacks a uniform built-in revocation checking mechanism.
To ensure timely protection for users on other platforms that might not receive platform updates, the team opted for an URGENT track security release, which similarly revoked trust in the affected certificates.
The team was initially alerted by an independent external researcher regarding unreported actions by Mozilla and other entities removing trust in the eight eMudhra intermediates. Mozilla independently confirmed this issue with the Go Security team, requesting that disclosure be delayed while a fix was prepared.
The finalized patch blocked the use of certificates chaining to the compromised intermediates. Due to the immediate exploitability and the belief that private keys would become public within hours, an immediate release was deemed the most prudent course of action, superseding the typical multi-day security release process.
In an effort to allow other defenders time to protect users without revealing exploitation methods, the initial communication was somewhat opaque, instructing users to upgrade immediately by warning they were "blocking trust in a small set of intermediate certificates due to specific security concerns around their operation."
The expedited release provided necessary security measures worldwide in under seven and a half hours from initial notification. Subsequent to this, on the morning of October 20, numerous independent researchers publicly disclosed the weakness of the private keys.
The organization noted that the issues encountered during the release process caused it to take just under four and a quarter hours from start to finish, exceeding expectations for this urgent scenario. Consequently, changes are being made to improve release efficiency.
The lack of platform API support for revocation checking on Linux was a significant factor driving the expedited release, prompting plans to prioritize parity in revocation support for Linux, potentially involving investigation into the upki project.
Operators running Go binaries that interact with network services via TLS should ensure they utilize the latest minor releases, as binaries built with Go 1.27.3 and 1.26.10 will automatically reject certificates from the compromised eMudhra intermediates.
