ci(vuln): set check-latest so govulncheck uses go1.26.5#32
Open
hstern wants to merge 1 commit into
Open
Conversation
The daily govulncheck scan fails on GO-2026-5856 (crypto/tls ECH privacy leak), fixed in go1.26.5. setup-go was resolving the Go version against the runner image (go1.26.4) because check-latest was false, so the fixed toolchain was never used. Enabling check-latest pulls the latest 1.26.x patch (1.26.5), whose crypto/tls is fixed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
What
Enable
check-latest: trueon thesetup-gostep invuln.yml.Why
The daily govulncheck scan is failing on GO-2026-5856 — Encrypted Client Hello privacy leak in
crypto/tls(found incrypto/tls@go1.26.4, fixed ingo1.26.5).setup-gowas resolving the Go version against theubuntu-latestrunner image, which still ships go1.26.4, becausecheck-latestwasfalse/unset.check-latest: truemakes it download the latest matching patch (go1.26.5), whosecrypto/tlscontains the fix, so the scan goes green — and future stdlib patch advisories clear automatically.Not a code vulnerability: the advisory is already fixed upstream; CI just needed to build with the patched toolchain.
🤖 Generated with Claude Code