Skip to content

fix(deps): upgrade go to 1.26.8 and vulnerable modules - #4510

Merged
stevenvegt merged 4 commits into
V6.2from
fix/deps-cves-v6.2
Sep 10, 2026
Merged

fix(deps): upgrade go to 1.26.8 and vulnerable modules#4510
stevenvegt merged 4 commits into
V6.2from
fix/deps-cves-v6.2

Conversation

@stevenvegt

@stevenvegt stevenvegt commented Sep 9, 2026

Copy link
Copy Markdown
Member

Summary

  • Go directive to 1.26.8 (the Dockerfile builder bump is in build(docker): upgrade to alpine 3.23.5, go 1.26.8 and apk upgrade #4507; the go-test and govulncheck workflows read the version from go.mod, so this is what makes the scheduled govulncheck green again)
  • Upgrade golang.org/x/crypto v0.53.0 to v0.55.0, golang.org/x/net v0.55.0 to v0.58.0 (required by x/crypto and grpc), google.golang.org/grpc v1.82.1 to v1.83.2, github.com/labstack/echo/v4 v4.15.0 to v4.15.3 and github.com/go-chi/chi/v5 v5.2.2 to v5.2.4
  • Release notes under Unreleased

Fixes the following vulnerabilities:

Advisory Package Description
GO-2026-6218 net/url Go stdlib, fixed in 1.26.6
GO-2026-6091 html/template Go stdlib, fixed in 1.26.6
GO-2026-6090 crypto/tls Go stdlib, fixed in 1.26.6
GO-2026-6089, GO-2026-5026 net/http Go stdlib, fixed in 1.26.6
GO-2026-6088 encoding/xml Go stdlib, fixed in 1.26.6
GO-2026-5972 encoding/asn1 Go stdlib, fixed in 1.26.6
CVE-2026-56854 golang.org/x/crypto fixed in v0.55.0
CVE-2026-46600 golang.org/x/net fixed in v0.56.0
CVE-2026-84303, CVE-2026-84304, CVE-2026-84445 google.golang.org/grpc fixed in v1.83.2
CVE-2026-55677 github.com/labstack/echo/v4 fixed in v4.15.3
CVE-2025-69725 github.com/go-chi/chi/v5 fixed in v5.2.4

The test job on V6.2 stays red until #4494 merges: it carries the fix for the stale nuts-node/cmd import in the docs test that has broken go-test on the branch since #4487.

Verification: go build ./... ok; govulncheck ./... reports 0 reachable vulnerabilities (was 7 stdlib). The module CVEs were never reachable according to govulncheck; they are fixed to clear image scanner reports. go test ./... passes except TestNetwork_checkHealth, which fails on this machine regardless of branch (local network environment).

Not for release yet; part of the batch of fixes before the next 6.2 patch tag, together with #4507.

Assisted-by: AI

The docs up-to-date test (#4493) was backported alongside the module
path change (#4487) and still imports the unsuffixed path, which makes
'go test ./docs/...' and 'go mod tidy' fail on V6.2.

Assisted-by: AI
A Trivy scan of the published 6.2.11 image flags the Go 1.26.5
standard library (7 advisories fixed in 1.26.6) and several modules.
govulncheck confirms only the stdlib advisories as reachable; the
module bumps clear the remaining image scanner findings.

Assisted-by: AI
The e2e workflow builds the image from this branch, and the go.mod
directive now requires 1.26.8. Same change as #4507; identical hunks
merge cleanly in either order.

Assisted-by: AI
Comment thread docs/pages/release_notes.rst Outdated

## Security
* Build with Go 1.26.8 to address `GO-2026-6218 <https://pkg.go.dev/vuln/GO-2026-6218>`_ (net/url), `GO-2026-6091 <https://pkg.go.dev/vuln/GO-2026-6091>`_ (html/template), `GO-2026-6090 <https://pkg.go.dev/vuln/GO-2026-6090>`_ (crypto/tls), `GO-2026-6089 <https://pkg.go.dev/vuln/GO-2026-6089>`_ and `GO-2026-5026 <https://pkg.go.dev/vuln/GO-2026-5026>`_ (net/http), `GO-2026-6088 <https://pkg.go.dev/vuln/GO-2026-6088>`_ (encoding/xml) and `GO-2026-5972 <https://pkg.go.dev/vuln/GO-2026-5972>`_ (encoding/asn1) in the Go standard library.
* Upgrade golang.org/x/crypto to v0.55.0 (CVE-2026-56854), golang.org/x/net to v0.58.0 (CVE-2026-46600), google.golang.org/grpc to v1.83.2 (CVE-2026-84303, CVE-2026-84304, CVE-2026-84445), github.com/labstack/echo/v4 to v4.15.3 (CVE-2026-55677) and github.com/go-chi/chi/v5 to v5.2.4 (CVE-2025-69725) as reported by image scanners. None of these code paths are reachable from the node according to govulncheck.

@reinkrul reinkrul Sep 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this also needs a newline after "Security" title, otherwise the list doesn't render. We also use dashes instead of *

Comment thread docs/pages/release_notes.rst
reStructuredText needs a blank line between the header and the bullet
list, otherwise the whole section renders as one paragraph. Also use
dashes for the bullets like the rest of the file.

Assisted-by: AI
@stevenvegt
stevenvegt merged commit e860d09 into V6.2 Sep 10, 2026
8 checks passed
@stevenvegt
stevenvegt deleted the fix/deps-cves-v6.2 branch September 10, 2026 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants