1. News
  2. Alerts
  3. Go · Security update
AlertGo · Security update3 min read

Go update blocks eight certificate keys, may break some connections

Go's emergency update makes programs refuse connections tied to eight certificate keys, so rebuilt software could suddenly fail to reach some sites and services.

By the Dashline deskSource: The Hacker News
Go update blocks eight certificate keys, may break some connections
Photo: The Hacker News
Act this week
What happenedGo released versions 1.27.3 and 1.26.10, which reject certificate chains passing through eight intermediate certificate authority keys.
Who is affectedAnyone running software built with Go, and any site or service whose certificate was issued under one of the eight blocked keys.
What to do
  1. 1Ask your developers or vendors whether any of your software is built with Go.
  2. 2Test connections to your key partners, portals and APIs before rolling out a rebuilt version.
  3. 3If a connection fails, ask the service owner to switch to a certificate from a different issuer.
  4. 4Apply the update once testing passes, since it was released as an emergency fix.

Go, a popular programming language, shipped an urgent update on October 20. Programs built with Go 1.27.3 or Go 1.26.10 will refuse to connect to any site or service whose certificate was issued under one of eight specific keys. If your business software is built with Go, rebuilding it on the new version could cut off some partner connections without warning.

What changed

A certificate is a digital ID that proves a website is the real one. Certificate authorities issue them, sometimes through middle layers called intermediates. Go's checker now rejects any chain that passes through eight of those intermediate keys. A blocked connection fails with the error "x509: no valid chains built."

The change has no off switch. It also appears to apply when a program uses its own list of trusted roots, so a private setup that deliberately trusts one of these keys will fail too. The Go team has not said whether that is intended.

What is known about the reason

The Go team says the keys belong to one certificate authority it has not named. It cites "specific security concerns around their operation." It used its URGENT track, which is reserved for its most serious issues, and recommends upgrading immediately. Its policy says there are no recent examples of that track, and it has not said why this one qualified.

Go's change lists only coded fingerprints of the keys. A commenter on the Go issue matched all eight to intermediates from eMudhra, an Indian certificate authority. Six are for websites and two are for signing code. The Hacker News has not independently checked that matching. Two days earlier, Mozilla blocked six eMudhra intermediates in Firefox's block list. Whether Chrome, Apple or Microsoft have acted is not established.

Who it affects

The main group is anyone running software built with Go. Existing programs keep their old behavior until they are rebuilt, so nothing breaks the moment the update is released. Some projects, including Bluesky's indigo, were already rebuilt on October 20. Go 1.25 and older are out of support and get no fixes, so a supported release is the only route.

Sites and services using certificates under the eight keys will need a certificate from a different intermediate before rebuilt Go programs can reach them. If your software is not built with Go, this change does not touch it.

What to do

The alert box above lists the steps. The short version is to find out whether you use Go software, test key connections first, then apply the update. No temporary workaround exists.

What is still unknown

  • What happened at the certificate authority is not public.
  • eMudhra has made no public statement, and its site had no notice as of October 20.
  • The Go team had not answered a user asking who the keys belong to.

eMudhra's older roots are trusted in the Chrome, Apple and Mozilla root stores. In September, a public review of its request to add ten new roots closed with no objections. Watch for a statement from eMudhra, Go or Mozilla.

The takeaway

Before rebuilding Go software on the new release, test connections to partners and services, because some may stop working.

More articles

You should really read these.

Next step

Let’s talk