From c0fe98a365f53dab93e1f7453fcb2956940f2529 Mon Sep 17 00:00:00 2001 From: Wynne Pirini Date: Thu, 22 Oct 2026 08:09:42 +1300 Subject: [PATCH] fix(build): move the Go toolchain to 1.26.10 for GO-2026-6809 Audit has been red on main since e5caca5, before any of this week's code changes, so it is not a source regression. govulncheck finds GO-2026-6809 in crypto/x509 at go1.26.9, fixed in go1.26.10, reached through internal/mailer/smtp.go:161 where the SMTP transport calls tls.Dialer and eventually x509.Certificate.Verify. go.mod pinned `toolchain go1.26.9` with `go 1.26.0`, so every CI run resolved the affected stdlib and the "clean-security-scan" claim in audit.yml failed on a vulnerability we do not control in our own code. Bump only the toolchain directive: the `go` line stays at 1.26.0 so the minimum language version does not move for something that is a patch-level stdlib fix. Verified under exactly go1.26.10: go build ./... passes and govulncheck ./... reports "No vulnerabilities found; your code is affected by 0 vulnerabilities". --- go.mod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/go.mod b/go.mod index ef47e3fc..062599c0 100644 --- a/go.mod +++ b/go.mod @@ -2,7 +2,7 @@ module github.com/calnode/calnode go 1.26.0 -toolchain go1.26.9 +toolchain go1.26.10 require ( github.com/disintegration/imaging v1.6.2