Skip to content

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

Merged
tannevaled merged 1 commit into
mainfrom
security-xnet-v0.60.0
Oct 11, 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 (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 in golang.org/x/net v0.60.0 and in the go1.27.2 standard library.

Called vulnerabilities, per module:

Before (default branch):

module called
. GO-2026-6617 GO-2026-6612 GO-2026-6611 GO-2026-6610 GO-2026-6603

After (this branch):

module called
. none

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

-go 1.27.1
+go 1.27.2
-	golang.org/x/net v0.59.0
+	golang.org/x/net v0.60.0

Other files:

  • README.md

Verification

  • .: go build -o /dev/null ./..., go vet ./..., go test ./... pass with go1.27.2 (darwin host).
  • Nothing was built into the tree (-o /dev/null); files were staged by name.

🤖 Generated with Claude Code

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: .: GO-2026-6617 GO-2026-6612 GO-2026-6611 GO-2026-6610 GO-2026-6603;
Called after:  .: none;

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tannevaled

Copy link
Copy Markdown
Contributor Author

Verified independently, both halves

Re-run here rather than taken on trust, with the settings this PR names
(GOTOOLCHAIN=go1.27.2 GOOS=linux GOARCH=amd64, govulncheck against the current
database):

origin/main (3cfa10a):

Vulnerability #1: GO-2026-6617   Found in: golang.org/x/net@v0.59.0   Fixed in: v0.60.0
Vulnerability #2: GO-2026-6612   Found in: golang.org/x/net@v0.59.0   Fixed in: v0.60.0
Vulnerability #3: GO-2026-6611   Found in: golang.org/x/net@v0.59.0   Fixed in: v0.60.0
Vulnerability #4: GO-2026-6610   Found in: golang.org/x/net@v0.59.0   Fixed in: v0.60.0
Vulnerability #5: GO-2026-6603   Found in: golang.org/x/net@v0.59.0   Fixed in: v0.60.0

Your code is affected by 5 vulnerabilities from 1 module.

This branch (cf4a3e6):

No vulnerabilities found.
Your code is affected by 0 vulnerabilities.

Same five identifiers, same direction. Merging.

One thing the scan found that this PR does not mention

GO-2026-5932   Found in: golang.org/x/crypto@v0.57.0   Fixed in: N/A

Not called — it lands in govulncheck's "modules you require, but your code
doesn't appear to call these" section on both sides, and Fixed in: N/A means
there is no version to move to. So it is correctly out of scope for this PR, and
worth writing down rather than leaving for the next person to rediscover: an
unfixable advisory that is present and unreachable is a thing to watch, not a
thing to bump.

🤖 Generated with Claude Code

@tannevaled
tannevaled merged commit 4872e01 into main Oct 11, 2026
9 checks passed
@tannevaled
tannevaled deleted the security-xnet-v0.60.0 branch October 11, 2026 15:46
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