Repository navigation
Pin the Go 1.27.3 toolchain so local builds skip vulnerable 1.27.0-1.27.2 [skip deploy] #no-deploy - #14
Open
SebastianLopezO wants to merge 1 commit into
Open
Pin the Go 1.27.3 toolchain so local builds skip vulnerable 1.27.0-1.27.2 [skip deploy] #no-deploy#14SebastianLopezO wants to merge 1 commit into
SebastianLopezO wants to merge 1 commit into
Conversation
…27.2 [skip deploy] #no-deploy go 1.26.10 sets a minimum, so a developer machine with Go 1.27.0 still compiled with crypto/x509 affected by CVE-2026-111943 (fixed in 1.26.10 and 1.27.3). The toolchain line makes the go command switch to 1.27.3, the same version as the Docker build stage.
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.
Caso
snyk testlocal sobrego.mod:SNYK-GOLANG-STDCRYPTOX509-21400137(CVE-2026-111943, CWE-299, Improper Check for Certificate Revocation), alta, CVSS 7.6
(
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N), corregida en 1.26.10 y 1.27.3.goa 1.26.10, pero esa línea fija un mínimo, no una rama. Un equipo con Go 1.27.0, 1.27.1 o1.27.2 cumple el mínimo y compila con un
crypto/x509afectado. Snyk lo detecta porque toma la versión de lalibrería estándar del
goinstalado.Análisis
golang:1.27.3-alpiney el CI con 1.26.10: producción y CI no están afectados. Elriesgo queda en binarios compilados en un equipo de desarrollo y en la deriva entre las tres versiones.
Cambio
toolchain go1.27.3engo.mod. ConGOTOOLCHAIN=auto(el valor por defecto), el comandogocambia solo a 1.27.3,la misma versión de la etapa de compilación del
Dockerfile.Verificación
go versiondentro del módulo:go1.27.3(descargado por el propiogo).go vet ./...ygo test ./...en verde;gofmt -l .vacío.snyk test: de 1 alta abierta a 0 (siguen las 3 medias de Echo ignoradas en.snykcon su mitigación en código).