Repository navigation
update-go-pkg: bump Go to 1.26.10 - #2178
Merged
Merged
Conversation
The private keys of eight eMudhra intermediate CAs were compromised, and the intermediates were revoked on 2026-10-18. Go 1.26.10 makes crypto/x509 reject chains that contain these intermediates (CVE-2026-111943, https://go.dev/issue/82345). Go doesn't check revocation, and the Alpine ca-certificates bundle in the runtime image still includes the eMudhra roots, so the Go release is what blocks these chains for the proxy's outbound TLS connections. Bump Go to 1.26.10 everywhere it is pinned (go.mod, Makefile, Dockerfiles, docker-compose.yml, appveyor.yml).
kinbiko
marked this pull request as ready for review
October 22, 2026 21:24
matt0x6F
approved these changes
Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the problem I am trying to address?
The private keys of eight eMudhra intermediate CAs were found to be compromised, and the intermediates were revoked on 2026-10-18 (Mozilla bug 2083449).
Six of them are TLS intermediates chaining to emSign Root TLS CA - G3.
Go 1.26.10 makes
crypto/x509reject chains that contain these intermediates (CVE-2026-111943, https://go.dev/issue/82345).Go doesn't check revocation, so without this release the proxy accepts certificates issued by the compromised keys.
The published images are built with older Go: athens v0.19.2 uses Go 1.26.2, and the newest athens-dev canary uses Go 1.26.9.
The runtime image's Alpine 3.24
ca-certificates-bundle(20260909-r0) still includes the eMudhra roots, so the Go release is the change that blocks these chains for the proxy's outbound TLS connections.How is the fix applied?
Bump Go from 1.26.9 to 1.26.10 everywhere it is pinned: go.mod, Makefile, cmd/proxy/Dockerfile, scripts/build-image/Dockerfile, Dockerfile.test, docker-compose.yml and appveyor.yml.
These are the same files changed in #2176.
Could a patch release be cut after merge so the published binaries and images include this change?