Repository navigation
build(go): build with Go 1.27.3 to remove a reachable standard-library vulnerability - #228
Merged
Merged
Conversation
…y vulnerability govulncheck reports GO-2026-6809 (crypto/x509 distrusts compromised intermediate certificates) as reachable in Go 1.27.2 through the CLI's diagnostic output path, so the release candidate and every source gate fail at go:vulncheck. Go 1.27.3 contains the fix. - go.mod: toolchain go1.27.3; the go directive and every module requirement are unchanged. - release/change-record.v2.json: the toolchain addition now states that release binaries are built with Go 1.27.3 and why; the pinned copy in internal/tools/releasechange/record_test.go is regenerated from it. Proof on this tree: A local npm run check sequence on darwin/arm64 passed (exit 0) on tree f7cfc5f with npm 12.2.0, CPython 3.15.0 and Go 1.27.3: 561/561 browser cases in Chromium, Firefox and WebKit with zero retries. One recorded deviation: the host firewall blocks Go-built binaries from the network, so the go:vulncheck step ran govulncheck against a vulnerability database snapshot fetched with curl (modified 2026-10-21T00:27:29Z) and found no vulnerabilities. With the same snapshot, Go 1.27.2 is reported affected by GO-2026-6809.
This was referenced Oct 22, 2026
iperev
marked this pull request as draft
October 25, 2026 19:53
iperev
marked this pull request as ready for review
October 25, 2026 20:10
Contributor
Author
Security prerequisite delivery
|
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.
Release blocker for 0.17.0. The release candidate run on
main(75caaf1) failed atgo:vulncheck: govulncheck reports GO-2026-6809 (crypto/x509 distrusts compromised intermediate certificates), published aftermain's last CI run, as reachable in Go 1.27.2 through the CLI's diagnostic output path. Go 1.27.3 contains the fix. Every source gate onmainwill fail the same way until this merges.What changes
go.mod:toolchain go1.27.3. Thegodirective and every module requirement are unchanged.release/change-record.v2.json: the toolchain addition states that release binaries are built with Go 1.27.3 and why; the pinned copy ininternal/tools/releasechange/record_test.gois regenerated from it.Compatibility
Not breaking. No command, flag, contract or output changes; release binaries are rebuilt with a patched standard library.
Proof
npm run checksequence on darwin/arm64 passed (exit 0) on treef7cfc5f6bd9awith npm 12.2.0, CPython 3.15.0 and Go 1.27.3: 561/561 browser cases in Chromium, Firefox and WebKit with zero retries.go:vulncheckstep ran govulncheck against a vulnerability-database snapshot fetched with curl (modified 2026-10-21T00:27:29Z): no vulnerabilities. With the same snapshot, Go 1.27.2 is reported affected by GO-2026-6809. Hosted CI runs govulncheck against the live database.Non-claims