Repository navigation
security: x/net v0.60.0 (reachable HTTP/2 advisories) - #38
Merged
Merged
Conversation
govulncheck v1.8.0 (GOTOOLCHAIN=go1.27.2 GOOS=linux) reported the HTTP/2 advisories GO-2026-6603/6610/6611/6612/6617 in golang.org/x/net as called from this repository. They are fixed in x/net v0.60.0 (x/sys, x/text and x/crypto move with it as a lockstep set) and in the go1.27.2 standard library. Called before: corpus: not scannable: `corpus/cmd/corpus` does not compile on the default branch either (`undefined: gluedWords`, main.go:192); not built by CI;.: GO-2026-6617 GO-2026-6612 GO-2026-6611 GO-2026-6610 GO-2026-6603; Called after: corpus: not scannable: `corpus/cmd/corpus` does not compile on the default branch either (`undefined: gluedWords`, main.go:192); not built by CI;.: none; Co-Authored-By: Claude Opus 5.5 <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.
Why
govulncheckv1.8.0 (GOTOOLCHAIN=go1.27.2 GOOS=linux govulncheck ./..., run in every module) reports the HTTP/2 advisories published 2026-10-08/09 as called (reachable from this code). They are fixed ingolang.org/x/netv0.60.0 and in the go1.27.2 standard library.Called vulnerabilities, per module:
Before (default branch):
corpus.After (this branch):
corpus.The remaining stdlib IDs in "before" (if any) are fixed by building with go1.27.2, which is what the scan used for both columns.
What changed
Other files:
.github/workflows/ci.ymlVerification
.:go build -o /dev/null ./...,go vet ./...,go test ./...pass with go1.27.2 (darwin host).corpus: does not compile on the default branch either (corpus/cmd/corpus/main.go:192: undefined: gluedWords; the function is defined nowhere in the repository) and no workflow builds it; only its x/net requirement andgodirective move here, the breakage is left for a separate change.-o /dev/null); files were staged by name.🤖 Generated with Claude Code