Skip to content

Build with Go 1.27.4, which fixes an HTTP server crash - #53

Merged
ssenerg merged 1 commit into
mainfrom
go-1.27.4
Nov 17, 2026
Merged

ssenerg merged 1 commit into
mainfrom
go-1.27.4

Conversation

@ssenerg

@ssenerg ssenerg commented Nov 17, 2026

Copy link
Copy Markdown
Owner

vulncheck fails on main and on every PR: Go 1.27.3's net/http has GO-2026-6859, where a race between http.MaxBytesReader and reading headers can crash an HTTP/1 server. govulncheck finds the web gateway, uploads to MinIO, FCM pushes and the admin server calling into it. Go 1.27.4 fixes it. Since main fails this required check, nothing has deployed since, and production still runs a 1.27.3 build.

What changes

  • go.mod: go 1.27.4. CI reads its Go version from here.
  • deployments/docker/Dockerfile and Dockerfile.template: the builder is golang:1.27.4-alpine3.24, pinned by its multi-platform index digest (sha256:70bd7ddea8b6…, the same platforms as the 1.27.3 pin).
  • README.md: the Go version in the requirements.

Checked

  • go build ./... and go test ./... on go1.27.4.
  • govulncheck@v1.8.0 ./..., as CI runs it: no vulnerabilities the code reaches (exit 0).

This unblocks #52, whose only failing check is this one.

🤖 Generated with Claude Code

govulncheck fails CI on Go 1.27.3's GO-2026-6859: a race between http.MaxBytesReader and reading headers can crash an HTTP/1 server, and the web gateway, uploads and pushes all reach it. Go 1.27.4 fixes it. The builder image moves to golang:1.27.4-alpine3.24, pinned by its index digest like before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ssenerg
ssenerg enabled auto-merge (squash) November 17, 2026 14:29
ssenerg added a commit that referenced this pull request Nov 17, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ssenerg
ssenerg merged commit c4317bc into main Nov 17, 2026
9 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