chore(security): bump the Go toolchain to 1.26.5 for GO-2026-5856#533
Merged
Conversation
Go 1.26.4's crypto/tls carries GO-2026-5856, an Encrypted Client Hello privacy leak, which the release validation gate's vulnerability scan flags and which blocks the release pipeline. Go 1.26.5 fixes it. Bump the toolchain directive in go.mod and e2e/go.mod; the go language directive is unchanged, and every CI job reads the version from go.mod via go-version-file, so the bump propagates without further edits. govulncheck is clean on 1.26.5. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
1 participant
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.
Problem
The release pipeline's validation gate (vulnerability scan) fails on GO-2026-5856, an Encrypted Client Hello privacy leak in
crypto/tlsshipped with Go 1.26.4 (the pinned toolchain). This blocked the nightly release from cutting a release-candidate, so the fleet never ran.Fix
Bump the
toolchaindirective fromgo1.26.4togo1.26.5(which fixes the CVE) ingo.modande2e/go.mod. Thegolanguage directive is unchanged, and every CI job reads the version viago-version-file: go.mod, so the bump propagates without further edits.Verification
Built on the auto-downloaded
go1.26.5:go build ./...,go test ./...,golangci-lint run ./...all clean;govulncheck ./...exits 0 with no vulnerabilities (GO-2026-5856 cleared). Not a code change; single-component output and behavior are unaffected.