Repository navigation
Update Go to 1.27.4 for GO-2026-6859 - #126
Merged
Merged
Conversation
Go 1.27.0-1.27.3 have an HTTP/1 server crash from a header race in net/http's MaxBytesReader (GO-2026-6859, CVE-2026-97054), fixed in go1.27.4. Bump the mise pin and lockfile, which tests and lint use, and go.mod's toolchain directive, which setup-go reads for the enclave binary in the Docker Build workflow and the PR docker-build check. https://pkg.go.dev/vuln/GO-2026-6859 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are identified for the Go 1.27.4 toolchain update.
No open issues 🎉
What changed in this PR
Updates the project’s Go toolchain from 1.27.3 to 1.27.4 to address GO-2026-6859, keeping mise-managed development and CI aligned with enclave builds.
Changes:
- Updates the mise pin and
go.modtoolchain directive together, while retaining thego 1.27minimum. - Refreshes Go download URLs and checksums for all five locked platforms.
| File | Description |
|---|---|
go.mod |
Sets the toolchain to Go 1.27.4 for builds. |
.mise/mise.lock |
Updates the locked Go version and platform artifacts. |
.mise/config.toml |
Pins mise-managed Go to 1.27.4. |
Review effort: Balanced
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
MaxBytesReaderheader race innet/http. It affects Go before 1.26.11 and 1.27.0 through 1.27.3.gopin,.mise/mise.lockand go.mod'stoolchaindirective move together, ascheck-go-versionrequires. Tests and lint get Go through mise; the docker-build PR check and Docker Build read thetoolchainline throughsetup-go(ci: install Go from go.mod's toolchain line in Docker Build #115), so the published enclave binary is built with 1.27.4. Thegodirective stays at1.27.Notes for reviewers
.mise/config.tomlsetsminimum_release_age = "7d"(Adopt mise for toolchain + tasks, pin GitHub Actions with ratchet #39, renamed in mise: rename install_before to minimum_release_age #116); that floor filters version resolution, and an exact pin installs from the lock, so this bump goes ahead of the floor on purpose for the security fix. The lock's checksums for all five platforms match https://go.dev/dl/.Pre-merge checklist
mise run //:check-go-versionpassesmise run //:lint,mise run //:tidy)mise run //:test)govulncheck ./...reports no vulnerabilities with Go 1.27.4Post-deploy/apply verification
setup-gowith Go 1.27.4 and pushed the enclave image (run 42958371349:Successfully set up Go version 1.27.4; pushed0a1f54d-arm64andlatest-arm64,sha256:55df1125501b84274d915af66faa2dfb0b5f7ed7a2efb54bf3f17c3dec12af74)🤖 Generated with Claude Code