
Go 1.27.3 and Go 1.26.10, released on October 20, 2026, block certificate chains that pass through eight intermediate certificate authority keys. Business IT teams should rebuild affected Go applications, update supported Go installations and check services that use certificates issued through the affected intermediates.
What Happened
According to The Go Programming Language’s vulnerability database, the two releases add protection against eight intermediate certificates that are no longer considered trustworthy. A Go application using either fixed release will reject a certificate chain that includes one of those intermediates, and, given the structure of the code, the filter also applies when a program supplies its own set of trusted roots. The Go team has not said whether that is intended.
Apple reports that the private keys of all eight intermediate CAs operated by eMudhra were compromised. Six issue TLS certificates, meaning someone with the keys could create certificates that appeared valid for any website, while two issue code-signing certificates. The eMudhra Intermediate CA Compromise tracker says the private keys were incorrectly generated, allowing anyone to recover them from the certificates, and that this would have been possible since the intermediates were created in April 2025.
Mozilla added six affected intermediate certificates to OneCRL on October 17. The Go team handled its release under its URGENT track and recommends upgrading immediately, citing security concerns around the certificates’ operation.
Are You Affected?
According to the Go vulnerability database, crypto/x509 is affected before go1.26.10 and from go1.27.0-0 before go1.27.3. Older applications keep the previous behavior until they are rebuilt, so checking only the Go version on a workstation may not show whether a deployed application contains the fix.
The affected certificate authorities include TLS intermediates under emSign Root TLS CA – G3: EM DV TLS CA – G3B, EM DV TLS CA – G3C, EM OV TLS CA – G3B, EM OV TLS CA – G3C, EM EV TLS CA – G3B and EM EV TLS CA – G3C. The other two are code-signing intermediates under emSign Root CS CA – G3: EM OV CS CA – G3B and EM OV CS CA – G3C.
Go’s verifier applies the block when it checks a certificate chain. A rejected chain returns the error x509: no valid chains built. Applications using their own trusted roots are also covered.
Apple’s advisory about the compromised eMudhra intermediate CAs says Apple devices automatically block the affected certificates in Safari, Mail and apps that use Apple’s networking and security frameworks. Some command-line tools, including curl and git, require updated macOS to stop accepting the certificates. Apps and tools with their own root certificate lists may need action from their developers.
What to Do Now
- Identify Go-based applications and services in the environment, including internal tools, websites, APIs, agents and client applications.
- Rebuild and redeploy affected applications with a supported Go release that includes the block.
- Check application and service logs for
x509: no valid chains builtand review failed outbound TLS connections. - Inventory issued certificates and identify any that chain through the eight affected intermediates. Obtain replacement certificates from a different intermediate for affected sites and services.
- Update macOS systems that rely on command-line tools such as curl, git, python3, ruby, perl and openssl. Apple’s advisory says macOS 27.2.1, 26.7.3 and 15.8.3 contain protection for these tools.
Background on the Compromised Intermediates
The compromise was possible because of faulty private-key generation. The Mozilla CA Program’s compromise tracker says there were no certificate transparency log entries for the affected intermediates during the period when the key generation was vulnerable. The tracker says CT-enforcing clients like Firefox, Chrome, Edge and Safari could not have been attacked during that period. It also says many clients outside of the browser ecosystem do not enforce Certificate Transparency, and that it is not known whether attackers exploited the flawed key generation to target those clients.
Apple says each of the six affected TLS intermediate CAs issued two certificates, for 12 affected TLS certificates in total. One certificate under each intermediate chains to emSign ECC Root CA – G3, while the other is cross-signed by Sectigo and chains to AAA Certificate Services. eMudhra and Sectigo revoked the affected certificates.
Go normally uses the root certificates supplied by the operating system. In narrower cases where a system trust store might not update without further action, the new crypto/x509 denylist returns an error when Verify encounters a known intermediate that is no longer considered trustworthy. The Go vulnerability database says the change contains no setting to turn the filter off.
Go 1.25 and older releases are out of support and get no fixes. The affected releases do not perform certificate revocation checking, so they also do not receive the protection through browser revocation lists such as OneCRL. Programs keep the old behavior until they are rebuilt with a release containing the new block.
FAQ
Which Go Versions Fix the Blocked Certificate Keys?
Go 1.27.3 and Go 1.26.10, both released on October 20, 2026, contain the fix. The Go vulnerability database lists crypto/x509 as affected before go1.26.10 and from go1.27.0-0 before go1.27.3. Go 1.25 and older releases are out of support and get no fixes.
Can the New Go Certificate Filter Be Turned Off?
No. The change contains no setting to turn the filter off, and the Go vulnerability database describes a denylist in crypto/x509 for known intermediate certificates that are no longer considered trustworthy.
Why Were the Eight eMudhra CA Keys Compromised?
The compromise tracker says the private keys were incorrectly generated by the CA, allowing anyone to recover them from the certificates. It says this would have been possible since the certificates were created in April 2025.
