Skip to content

Move to Go 1.26.10 and x/net v0.60.0 to clear govulncheck findings - #50

Merged
m-messer merged 1 commit into
mainfrom
fix/go-1.26-vulns
Oct 20, 2026
Merged

m-messer merged 1 commit into
mainfrom
fix/go-1.26-vulns

Conversation

@m-messer

Copy link
Copy Markdown
Member

The Vulnerability Scan job added in #35 fails on main. govulncheck traces 9 vulnerabilities to code shimmy actually runs (the HTTP server, the muEd handlers and cmd.run).

Where Was Fixed in
Standard library: net/http, net/textproto, crypto/tls (GO-2026-6603, 6605, 6607, 6608, 6610–6613, 6617) go1.25.14 go1.26.9
golang.org/x/net HTTP/2 (6 of the above) v0.58.0 v0.60.0

The Go 1.25 line has no fix for these, so this moves shimmy to Go 1.26.

Changes

  • go.mod: go 1.26.0, toolchain go1.26.10 and golang.org/x/net v0.60.0. go mod tidy also brought in the matching x/sync, x/sys and x/text bumps.
  • Dockerfile: the builder and test-sandbox stages now use golang:1.26, so the shipped image is built with the fixed toolchain. CI's setup-go steps already read the version from go.mod.

Testing

On go1.26.10, go build ./..., go vet ./... and go test ./... all pass, and govulncheck ./... reports "No vulnerabilities found."

Once this is merged, shimmy v0.0.9 gets released from main.

🤖 Generated with Claude Code

govulncheck reported 9 reachable vulnerabilities in net/http,
net/textproto and crypto/tls (fixed in go1.26.9) and in x/net's HTTP/2
code (fixed in v0.60.0). Bump the go directive, toolchain and the
Docker builder images to 1.26 so the shipped binaries pick up the fixes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@m-messer
m-messer merged commit 42c7d64 into main Oct 20, 2026
8 checks passed
@m-messer
m-messer deleted the fix/go-1.26-vulns branch October 20, 2026 14:11
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