build: bump Go 1.26.10 + ca-certificates for eMudhra CA distrust (GO-2026-6809)

Why

The private keys of eight eMudhra intermediate CAs were disclosed as compromised (2026-10-20), and trust stores are now distrusting them. govulncheck fails on every branch because GO-2026-6809 is now in the vuln DB. That advisory is the matching crypto/x509 fix, shipped in go1.26.10. The vulnerable code is reachable via bifrost/pkg/chainclients/monero/sidecar.*Server.Start -> net/http -> crypto/tls -> x509.Certificate.Verify. Each MR branch currently gets its own Go bump (e.g. thornode-private !74 (merged) / !119 (merged)); this fixes it once on develop.

What

Toolchain, images and CI only. No code changes.

  1. ca-certificates 20230311+deb12u1 -> 20250419~deb12u2 (bookworm-security, DLA-4845-1) in build/docker/Dockerfile and tools/events/Dockerfile. This removes the roots the compromised intermediates chain to from the image trust store. Go reads the OS trust store on Linux, and so does curl. The version resolves on the pinned base debian:bookworm-20260610-slim (checked with apt-cache policy).
  2. Go 1.26.9 -> 1.26.10 everywhere it is pinned: the go.mod toolchain, .go-version, test/simulation/go.mod, .gitlab-ci.yml images, the Dockerfiles, .trunk/trunk.yaml, scripts and docs. Go 1.26.10 blocks the eight intermediates in x509.Verify itself, and this is what clears govulncheck. go build ./... passes on go1.26.10.

This is the develop counterpart of !5256 (merged) (mainnet-3.21.1), with the same pins.

🤖 Generated with Claude Code

Edited by Son of Odin

Merge request reports

Loading
Loading