Skip to content

security: x/net v0.60.0 (reachable HTTP/2 advisories) - #14

Merged
tannevaled merged 1 commit into
mainfrom
security-xnet-v0.60.0
Oct 10, 2026
Merged

tannevaled merged 1 commit into
mainfrom
security-xnet-v0.60.0

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

Why

govulncheck (v1.8.0, GOOS=linux, toolchain go1.27.2) finds these advisories called (reachable from this repository's code, mostly through the gRPC/HTTP/2 server transport):

  • Before: GO-2026-6603[golang.org/x/net] GO-2026-6610[golang.org/x/net] GO-2026-6611[golang.org/x/net] GO-2026-6612[golang.org/x/net] GO-2026-6617[golang.org/x/net]
  • After: none

What

 .github/workflows/ci.yml | 2 +-
 go.mod                   | 4 ++--
 go.sum                   | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)
  • Module upgrades: x/net v0.60.0 (reachable HTTP/2 advisories)
  • go directive raised to 1.27.2 where it named an older 1.27 patch release (the standard-library advisories are fixed by go1.27.2).

Verified locally

go build -o /dev/null ./... (linux and darwin), go vet ./... (linux), go test ./..., then govulncheck ./... again for the "after" line.

🤖 Generated with Claude Code

govulncheck (GOOS=linux, go1.27.2) reported these advisories as called
from this repository's code; the upgrade removes them.

Called before: GO-2026-6603[golang.org/x/net] GO-2026-6610[golang.org/x/net] GO-2026-6611[golang.org/x/net] GO-2026-6612[golang.org/x/net] GO-2026-6617[golang.org/x/net]
Called after:  none

The go directive is raised to 1.27.2 where it named an older 1.27 patch
release, so the standard-library advisories fixed in go1.27.2 stay fixed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit ca8ca5e into main Oct 10, 2026
8 checks passed
@tannevaled
tannevaled deleted the security-xnet-v0.60.0 branch October 10, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant