Repository navigation
Conversation
govulncheck (run inline in the required build-test check, pulling the live vuln DB) reports GO-2026-6859 against net/http@go1.26.10 β an HTTP/1 server crash from a MaxBytesReader header race, fixed in net/http@go1.26.11. The advisory was disclosed 2026-11-11, so it turned the build-test check red repo-wide, including on an unmodified main, blocking every open PR under strict branch protection. Bump the toolchain to the fix release 1.26.11 across every surface: the go.mod go directive and the setup-go go-version in all four workflows (ci, release, codeql, govulncheck). Verified locally under go1.26.11: govulncheck ./... reports no vulnerabilities, and gofmt/go vet/go build/go test ./... -race are all clean. No code or behavior change beyond the version bump.
cwest
left a comment
There was a problem hiding this comment.
No changes needed.
This does exactly what it says: bumps the Go toolchain from 1.26.10 to 1.26.11 across go.mod and the setup-go step in all four workflows, with a matching CHANGELOG entry. Nothing else moves.
I reproduced the advisory both ways against this tree. On base main under go1.26.10, govulncheck reports GO-2026-6859 in net/http, fixed in 1.26.11. On this branch under go1.26.11, govulncheck comes back clean. The CHANGELOG description of the bug (an HTTP/1 MaxBytesReader header race) matches the upstream advisory. gofmt, go vet, go build, and go test ./... -race are all green under 1.26.11, and there's no behavior change beyond the version strings.
The four required checks (build-test, lint, analyze (go), site) are green; build-test, the one this is meant to unblock, is back to passing. The skill-contract check is red, but it's red on unmodified main too, from a 403 off the okfctl.dev install path, so it's unrelated to this change and isn't a required check.
Why
govulncheck(run inline in the requiredbuild-testcheck, pulling the live vuln DB) reports GO-2026-6859 againstnet/http@go1.26.10β an HTTP/1 server crash from aMaxBytesReaderheader race, fixed innet/http@go1.26.11. The advisory was disclosed 2026-11-11, so it turnedbuild-testred repo-wide β including on an unmodifiedmainβ blocking every open PR understrictbranch protection. This is a standard-library advisory, not a code defect in any PR.What
Bump the Go toolchain to the fix release 1.26.11 across every surface:
go.modβgo 1.26.10β1.26.11(no separatetoolchaindirective present).github/workflows/{ci,release,codeql,govulncheck}.ymlβ everysetup-gogo-version: '1.26.10'β'1.26.11'(8 occurrences total;ci.ymlhas 4)CHANGELOG.mdβ a### Buildentry under[Unreleased], matching the house pattern of the prior 1.26.6β1.26.10 entryNo code or behavior change beyond the version bump.
Verification (run locally under go1.26.11)
Root cause proven both directions:
govulncheck ./...Vulnerability #1: GO-2026-6859 β¦ Fixed in: net/http@go1.26.11No vulnerabilities found.Under go1.26.11:
govulncheck ./...β No vulnerabilities found (GO-2026-6859 cleared)gofmt -l .β cleango vet ./...β cleango build ./...β cleango test ./internal/okf/ ./cmd/ -run Conformance -raceβ pass (spec-conformance gate)go test ./... -raceβ all packages passokfctl --version/--helprun cleanDone when
govulncheck ./...no longer reports GO-2026-6859 on main β (verified)build-testcheck goes green (expected once CI runs the new head)