Go Issues Emergency Update Blocking Eight CA Keys Over Undisclosed Security Concerns
Go 1.27.3 and Go 1.26.10, released on October 20, make Go's certificate verifier reject any certificate chain that passes through one of eight intermediate certificate authority keys.
Go 1.27.3 and Go 1.26.10, released on October 20, make Go's certificate verifier reject any certificate chain that passes through one of eight intermediate certificate authority keys.
Programs built on the new release will refuse connections to sites and services whose certificates were issued under those keys.
The Go team says the keys belong to one certificate authority it has not named, and that it is blocking them because of It handled the fix on its URGENT track , the one reserved for its most serious issues, and recommends upgrading immediately.
Two days earlier, on October 17, Mozilla added six intermediate certificates issued by eMudhra's emSign Root TLS CA - G3 to OneCRL , the list Firefox uses to block certificates.
By that matching, six are TLS intermediates issued under the same emSign Root TLS CA - G3 that Mozilla's entries name, and two are code-signing intermediates under emSign Root CS CA - G3: The Hacker News has not independently checked the hashes against the certificates.
Projects including Bluesky's indigo were rebuilt on the new releases on October 20.
It is applied in Go's own verifier and in the macOS and Windows code paths that hand verification to the operating system.
On the issue, one user asked for the committed patch to explain The Go team had not replied as of October 20.
Mozilla's six entries carry the same issuing root, but Mozilla's records do not name the six certificates.
It hashes each certificate's public key rather than the certificate itself, so a cross-signed copy of one of the eight keys, the same key signed by a different root, is caught as well.
Given the structure of the code, it also applies when a program supplies its own set of trusted roots, so a private deployment that intentionally trusts one of the eight keys will fail too.
Go's security policy defines URGENT track issues as or flaws being actively exploited with severe damage, and says there are no recent examples.
Its roots emSign Root CA - G1 and emSign ECC Root CA - G3 are in the Chrome , Apple , and Mozilla root stores.
It also does not read the block lists browsers use, such as the CRLSets Chrome used against rogue Google certificates this month.
What happened
Go 1.27.3 and Go 1.26.10, released on October 20, make Go's certificate verifier reject any certificate chain that passes through one of eight intermediate certificate authority keys.
Programs built on the new release will refuse connections to sites and services whose certificates were issued under those keys.
The Go team says the keys belong to one certificate authority it has not named, and that it is blocking them because of It handled the fix on its URGENT track , the one reserved for its most serious issues, and recommends upgrading immediately.
What changed
Two days earlier, on October 17, Mozilla added six intermediate certificates issued by eMudhra's emSign Root TLS CA - G3 to OneCRL , the list Firefox uses to block certificates.
By that matching, six are TLS intermediates issued under the same emSign Root TLS CA - G3 that Mozilla's entries name, and two are code-signing intermediates under emSign Root CS CA - G3: The Hacker News has not independently checked the hashes against the certificates.
Projects including Bluesky's indigo were rebuilt on the new releases on October 20.
Who is affected
It is applied in Go's own verifier and in the macOS and Windows code paths that hand verification to the operating system.
On the issue, one user asked for the committed patch to explain The Go team had not replied as of October 20.
Why it matters
Mozilla's six entries carry the same issuing root, but Mozilla's records do not name the six certificates.
It hashes each certificate's public key rather than the certificate itself, so a cross-signed copy of one of the eight keys, the same key signed by a different root, is caught as well.
Technical details
Given the structure of the code, it also applies when a program supplies its own set of trusted roots, so a private deployment that intentionally trusts one of the eight keys will fail too.
Go's security policy defines URGENT track issues as or flaws being actively exploited with severe damage, and says there are no recent examples.
Its roots emSign Root CA - G1 and emSign ECC Root CA - G3 are in the Chrome , Apple , and Mozilla root stores.
Response
It also does not read the block lists browsers use, such as the CRLSets Chrome used against rogue Google certificates this month.
Blocking a key therefore means shipping it in a release, and programs keep the old behavior until they are rebuilt.
What security teams should do
Certificates logged for eMudhra's own domains, including emsign.com and emudhra.com, chain through other eMudhra intermediates, according to certificate transparency records The Hacker News checked on October 20.
No temporary workaround exists in any source, and the filter cannot be disabled.
What remains unknown
The Go team has not said whether that is intended.
Go has not said which of those applied.
Attribution
The Hacker News: Go 1.27.3 and Go 1.26.10, released on October 20, make Go's certificate verifier reject any certificate chain that passes through one of eight intermediate certificate authority keys.
What to watch next
Watch for additional victim details, indicators of compromise and follow-on exploitation reports.
Watch for revised vendor guidance, fixed versions and mitigation updates.