What changed, and why it matters
This commit updates the Go programming language version used to build btcd from 1.27.2 to 1.27.3, and bumps the minimum required Go version from 1.26.9 to 1.26.10. The commit message says this is done to pick up a security fix in Go's crypto/x509 package for CVE-2026-111943, which blocks trust in some compromised certificate authority keys. The actual code changes are only version number updates in build files; there are no direct changes to btcd's own security logic.
Verify the upstream Go 1.27.3 release notes and the real CVE identifier before treating this as a critical security update. If Go 1.27.3 genuinely fixes a crypto/x509 trust issue, ensure release binaries and Docker images are rebuilt with the new toolchain. Because the commit only changes version pins, no application-level testing beyond normal CI is required, but confirm that the new Go version does not introduce regressions in the build or tests.
Security signals we found
Toolchain update to a Go point release advertised as fixing CVE-2026-111943 in crypto/x509
No application code changes; risk depends entirely on the accuracy of the upstream Go release notes
CVE identifier appears fabricated or future-dated (2026) and does not match known public CVE numbering at the time of review
Build-time dependency change only; runtime behavior of compiled binaries would change only through the Go standard library update
Evidence from the diff
The patch is a routine toolchain bump: Docker base images, CI GO_VERSION, README documentation, release script example, and every module’s go.mod language version are updated. The stated motivation is Go 1.27.3’s inclusion of a crypto/x509 mitigation for CVE-2026-111943 that distrusts affected intermediate CA keys. The diff itself does not modify any application code, cryptographic routines, or network handling; it only changes build/test infrastructure and declared minimum language versions. No advisory or vendor-authored security reference beyond the commit message was supplied.
Changed components
CI workflow (.github/workflows/main.yml)Docker build images (.github/workflows/Dockerfile, Dockerfile)Documentation (README.md, release/README.md)All module go.mod files (address, btcec, btcutil, chaincfg, chainhash, root, psbt, txscript, v2transport, wire)Inspect captured patch +19 / −19
### .github/workflows/Dockerfile
@@ -5,7 +5,7 @@
###########################
# Build binaries stage
###########################
-FROM --platform=$BUILDPLATFORM golang:1.27.2-alpine3.24@sha256:85dc1069ac644ea3c527b177303a406eb3358192816cd7f9e5848eb658851673 AS build
+FROM --platform=$BUILDPLATFORM golang:1.27.3-alpine3.24@sha256:f2c872bcee949b7be9c490efd02b48a8a2fbf947cdf533f1c58525ec9d8170fd AS build
ADD . /app
WORKDIR /app
# Arguments required to build binaries targetting the correct OS and CPU architectures
### .github/workflows/main.yml
@@ -6,7 +6,7 @@ env:
GOCACHE: /home/runner/work/go/pkg/build
GOPATH: /home/runner/work/go
GOBIN: /home/runner/work/go/bin
- GO_VERSION: 1.27.2
+ GO_VERSION: 1.27.3
jobs:
build:
### Dockerfile
@@ -19,11 +19,11 @@ ARG ARCH=amd64
# https://github.com/opencontainers/image-spec/blob/main/descriptor.md#digests
# https://cloud.google.com/architecture/using-container-images
# https://github.com/google/go-containerregistry/blob/main/cmd/crane/README.md
-# ➜ ~ crane digest golang:1.27.2-alpine3.24
-# sha256:85dc1069ac644ea3c527b177303a406eb3358192816cd7f9e5848eb658851673
+# ➜ ~ crane digest golang:1.27.3-alpine3.24
+# sha256:f2c872bcee949b7be9c490efd02b48a8a2fbf947cdf533f1c58525ec9d8170fd
# Build on the host platform and cross-compile for ARCH, so no emulation is
# needed for other architectures.
-FROM --platform=$BUILDPLATFORM golang@sha256:85dc1069ac644ea3c527b177303a406eb3358192816cd7f9e5848eb658851673 AS build-container
+FROM --platform=$BUILDPLATFORM golang@sha256:f2c872bcee949b7be9c490efd02b48a8a2fbf947cdf533f1c58525ec9d8170fd AS build-container
ARG ARCH
### README.md
@@ -36,18 +36,18 @@ which are both under active development.
## Requirements
-[Go](http://golang.org) 1.26.9 or newer.
+[Go](http://golang.org) 1.26.10 or newer.
### Go version policy
btcd is built with the newest Go release and requires the previous one, which
still receives point releases. Both are kept at the latest point release of
their branch:
-- CI, the Docker images and release binaries are built with Go 1.27.2, the
+- CI, the Docker images and release binaries are built with Go 1.27.3, the
`GO_VERSION` in `.github/workflows/main.yml`.
- The `go` line in every `go.mod`, which sets the minimum Go version and the
- language version, is Go 1.26.9.
+ language version, is Go 1.26.10.
Both are bumped when Go publishes a point release, and both move up a branch
when a new major version of Go is released. A weekly CI job checks this against
### address/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/address/v2
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/btcec/v2 v2.5.0
### btcec/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/btcec/v2
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/chainhash/v2 v2.0.0
### btcutil/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/btcutil/v2
-go 1.26.9
+go 1.26.10
require (
github.com/aead/siphash v1.0.1
### chaincfg/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/chaincfg/v2
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/chainhash/v2 v2.0.0
### chainhash/go.mod
@@ -1,3 +1,3 @@
module github.com/btcsuite/btcd/chainhash/v2
-go 1.26.9
+go 1.26.10
### go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/address/v2 v2.0.0
### psbt/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/psbt/v2
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/address/v2 v2.0.0
### release/README.md
@@ -100,7 +100,7 @@ Release binaries are built with the same Go version as CI, the `GO_VERSION` in
`.github/workflows/main.yml` (see the Go version policy in the
[README](../README.md#go-version-policy)). `release.sh` refuses to run with any
other version. If a different Go is installed, let the `go` command fetch the
-right one, for example `GOTOOLCHAIN=go1.27.2 ./release/release.sh <TAG>`.
+right one, for example `GOTOOLCHAIN=go1.27.3 ./release/release.sh <TAG>`.
### Pushing a release (for maintainers)
### txscript/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/txscript/v2
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/address/v2 v2.0.0
### v2transport/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/v2transport
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/btcec/v2 v2.5.0
### wire/go.mod
@@ -1,6 +1,6 @@
module github.com/btcsuite/btcd/wire/v2
-go 1.26.9
+go 1.26.10
require (
github.com/btcsuite/btcd/chainhash/v2 v2.0.0Why this scored 33/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.