Repository navigation
build(deps): move Go to 1.26.9 for GO-2026-6617 - #313
Merged
Merged
Conversation
GO-2026-6617 (CVE-2026-97032, an HTTP/2 server crash in net/http) affects every release before 1.26.9 and 1.27.0-1.27.1. go.mod and both images were on 1.26.6; CI reads the version from go.mod, so build, tests and images now all run on 1.26.9. 1.27.2 would exclude both lines' vulnerable releases, but no staticcheck release (nor go-tools master) reads Go 1.27 export data yet, nor does gosec v2.28.0, so it would cost the whole lint gate. The residual (a local 1.27.0/1.27.1 build satisfies the floor) and the reopening condition are recorded in docs/DECISIONS.md. Closes #312 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
Closes #312. Segurança: CVE-2026-97032 / GO-2026-6617, um crash no servidor HTTP/2 do
net/http.go.mod,Dockerfileeweb/Dockerfile: 1.26.6 → 1.26.9. Como a CI usago-version-file, o build, os testes e as imagens rodam nessa versão.staticchecknem omasterdo go-tools leem o export data do Go 1.27, e o gosec v2.28.0 também não. Subir para 1.27.2 removeria o gate de lint. O resíduo (um build local com 1.27.0/1.27.1 satisfaz o piso) e a condição para reabrir estão emdocs/DECISIONS.md.DECISIONS.mdtambém registra um falso positivo G703 que o gosec mais novo vai apontar nospaHandler, para quando a versão dele for atualizada.Exposição baixa: nenhum binário serve TLS nem h2c.
Plano de teste (todos com o código de saída conferido)
go buildego vetem go1.26.9;go mod tidy -difflimpostaticcheck@v0.8.1, com e sem-tags=integration: exit 0gosec@v2.28.0, com e sem-tags=integration, exatamente como omake gosec: exit 0, 0 issuesgovulncheck@v1.7.0: exit 0go test -race ./...docker build .(imagem da API) compila emgolang:1.26.9-alpine🤖 Generated with Claude Code