fix: bump toolchain to go1.26.4 to address stdlib security vulnerabilities#312
Open
Farjaad wants to merge 3 commits into
Open
fix: bump toolchain to go1.26.4 to address stdlib security vulnerabilities#312Farjaad wants to merge 3 commits into
Farjaad wants to merge 3 commits into
Conversation
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.
Summary
Bumps the Go toolchain from
go1.26.2togo1.26.4to remediate 8 high-severity stdlib vulnerabilities flagged by Grype on theopslevel-runnercontainer image.Also includes a transitive bump of
golang.org/x/netfromv0.54.0tov0.55.0pulled in bygo mod tidy.Background
Grype scans the published container image and detects the Go toolchain version embedded in the compiled binary metadata. When the toolchain version is older than the version that patched a known CVE, Grype flags it — regardless of whether the vulnerable code path is actually reachable. The only fix is to recompile with a patched toolchain.
The
v2026.7.7release was built withtoolchain go1.26.2, which predates three subsequent Go security patch releases.Note:
go1.26.5(released 2026-07-07) is skipped per our one-week cooloff policy. It will be picked up in a follow-up bump.Vulnerabilities Fixed
All 8 are Go standard library bugs. They are fixed by the toolchain upgrade alone — no application code changes are required.
net/mail— DoS viaconsumePhrasewhen parsing RFC 5322 email addressesnet/mail— excessive CPU/memory inParseAddress,ParseAddressList,ParseDategolang.org/x/net/http2— infinite loop onSETTINGS_MAX_FRAME_SIZE=0net—Dial/LookupPortpanic on NUL input on Windowsnet— double-free crash in cgo DNS resolver on very long CNAME responsecrypto/x509— quadratic cost inVerifyHostnamewith large DNS SAN listsmime— excessive CPU decoding malformed MIME headers with invalid encoded-wordsnet/textprotoFull Go 1.26 release history: https://go.dev/doc/devel/release#go1.26
What Changed
Safety
Go patch releases are security/bug-fix only — no API changes, no breaking changes. This was verified by:
go build ./...succeedsgovulncheck ./...reports no vulnerabilities