Skip to content

build(deps): bump golang.org/x/net from v0.52.0 to v0.53.0#1269

Merged
rdimitrov merged 2 commits intomodelcontextprotocol:mainfrom
rdimitrov:fix/govulncheck-stdlib-1.26.3
May 8, 2026
Merged

build(deps): bump golang.org/x/net from v0.52.0 to v0.53.0#1269
rdimitrov merged 2 commits intomodelcontextprotocol:mainfrom
rdimitrov:fix/govulncheck-stdlib-1.26.3

Conversation

@rdimitrov
Copy link
Copy Markdown
Member

@rdimitrov rdimitrov commented May 8, 2026

Summary

Bumps golang.org/x/net from v0.52.0 to v0.53.0 to address GO-2026-4918 (HTTP/2 transport infinite loop on bad SETTINGS_MAX_FRAME_SIZE). go mod tidy also pulls golang.org/x/crypto to v0.50.0 and golang.org/x/text to v0.36.0.

Why now

govulncheck is failing on main and every open Dependabot PR (#1263, #1264, #1265) after the 2026-05 Go security release. The findings split into:

  • One we controlgolang.org/x/net@v0.52.0 → fixed in v0.53.0. Addressed here.
  • Six stdlib findings (GO-2026-4986, 4982, 4980, 4977, 4971, and the stdlib half of 4918) — all fixed in go1.26.3. We deliberately do not pin a Go patch in the workflow: go-version: 'stable' will pick up 1.26.3 automatically once the actions/go-versions manifest catches up, with no workflow maintenance.

Test plan

  • go build ./...
  • go vet ./...
  • GOTOOLCHAIN=go1.26.3 govulncheck ./... → "No vulnerabilities found."

🤖 Generated with Claude Code

rdimitrov and others added 2 commits May 8, 2026 14:26
…check

govulncheck started failing CI (incl. all open Dependabot PRs) after the
2026-05 Go security release. Six stdlib vulnerabilities (GO-2026-4986,
4982, 4980, 4977, 4971, 4918) require go1.26.3, and GO-2026-4918 also
requires golang.org/x/net@v0.53.0.

The setup-go 'stable' channel is still resolving to 1.26.2 from the
runner toolchain cache; pin '>=1.26.3' in ci.yml so govulncheck and the
build/test jobs always see a patched stdlib.

Verified locally with GOTOOLCHAIN=go1.26.3: "No vulnerabilities found."

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Keep go-version: 'stable' so future Go security releases land in CI
automatically instead of requiring a workflow edit. The stdlib portion
of the alerts will clear once the actions/go-versions manifest publishes
1.26.3; the third-party x/net bump in this branch already addresses the
piece we control.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rdimitrov rdimitrov changed the title ci: bump Go to >=1.26.3 and x/net to v0.53.0 to fix govulncheck build(deps): bump golang.org/x/net to v0.53.0 (CVE-2026-... / GO-2026-4918) May 8, 2026
@rdimitrov rdimitrov changed the title build(deps): bump golang.org/x/net to v0.53.0 (CVE-2026-... / GO-2026-4918) build(deps): bump golang.org/x/net from v0.52.0 to v0.53.0 May 8, 2026
@rdimitrov rdimitrov merged commit f5fe2e9 into modelcontextprotocol:main May 8, 2026
2 checks passed
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