Skip to content

fix: update golang.org/x/net to v0.62.0 - #1087

Open
vitoramaral10 wants to merge 1 commit into
gotify:masterfrom
vitoramaral10:bugfix/bump-x-net-http2-advisories
Open

vitoramaral10 wants to merge 1 commit into
gotify:masterfrom
vitoramaral10:bugfix/bump-x-net-http2-advisories

Conversation

@vitoramaral10

Copy link
Copy Markdown

govulncheck ./... on master reports five advisories in golang.org/x/net v0.58.0 that the server's HTTP/2 handling reaches:

  • GO-2026-6603 (CVE-2026-78659): HTTP/2 server memory exhaustion due to Trailer headers
  • GO-2026-6610 (CVE-2026-78660): HTTP/2 transport accepts malformed framing-related headers
  • GO-2026-6611 (CVE-2026-78669): excessive CPU consumption from repeated initial window changes
  • GO-2026-6612 (CVE-2026-78663): double flow control refund on HTTP/2 server streams
  • GO-2026-6617 (CVE-2026-97032): HTTP/2 server crash due to HPACK encoder race

All are fixed in v0.60.0. This bumps x/net to the latest v0.62.0; go mod tidy also moves x/crypto, x/sync, x/sys and x/text to the versions it requires. No code changes.

The latest release (v3.1.1) ships x/net v0.55.0 and is built with Go 1.26.0, so it is affected as well, together with the Go standard library advisories fixed since 1.26.0. A release built with this change and the current GO_VERSION (or 1.27.4, once a gotify/build image exists for it) would cover both.

Testing:

  • govulncheck ./...: no vulnerabilities found (was 5).
  • go test --race ./...: all packages pass, with the UI built via yarn build.

The router reaches HTTP/2 code in x/net v0.58.0 that is affected by
GO-2026-6603, GO-2026-6610, GO-2026-6611, GO-2026-6612 and
GO-2026-6617. The fixes landed in v0.60.0.
@vitoramaral10
vitoramaral10 requested a review from a team as a code owner November 15, 2026 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant