Skip to content

[SSPROD-73763] fix: bump Go to 1.26.10 and x/text, x/sys in linux-bench-dependency - #32

Merged
figarocorso merged 2 commits into
masterfrom
SSPROD-73763-bump-go-1.26.9
Oct 28, 2026
Merged

figarocorso merged 2 commits into
masterfrom
SSPROD-73763-bump-go-1.26.9

Conversation

@figarocorso

@figarocorso figarocorso commented Oct 28, 2026 •

Copy link
Copy Markdown

Human TL;DR: linux-bench-dependency ships a linux-bench binary built with Go 1.25.11 and old x/text/x/sys, which fails the Jenkins vuln scan of secure-backend's compliance-benchmark-runner. Bump to Go 1.26.10 and latest x/text, x/sys.

Proposed changes

Jira: SSPROD-73763

The secure-backend Vulnerabilities Check - compliance Jenkins stage fails on compliance-benchmark-runner (blocking e.g. draios/secure-backend#60705). Part of the reported CVEs come from the linux-bench binary copied from linux-bench-dependency:1.1.0.15:

  • Go 1.25.11 → fix in 1.26.10 (2 Critical, 16 High)
  • golang.org/x/text v0.30.0 → fix in v0.39.0
  • golang.org/x/sys v0.37.0 → fix in v0.44.0
File Change
Dockerfile (+ _linux_arm64, _linux_s390x) golang:1.25.11 → 1.26.10 (builder of the scanned binary)
go.mod / go.sum go 1.26.10; x/sys v0.49.0, x/text v0.43.0
.github/workflows/build.yml, release.yml go-version: 1.26.10

go build ./..., go vet ./... and go test ./... pass locally.

Follow-up (after merge)

  1. Tag 1.1.0.16 and run the secure/compliance/compliance-linux-bench Jenkins job to publish linux-bench-dependency:1.1.0.16.
  2. Bump LINUX_BENCH_TAG in secure-backend compliance/cmd/benchmark-runner/Dockerfile (SSPROD-73763 PR).

@figarocorso
figarocorso requested a review from a team as a code owner October 28, 2026 09:38
@figarocorso figarocorso changed the title [SSPROD-73763] fix: bump Go to 1.26.9 and x/text, x/sys in linux-bench-dependency [SSPROD-73763] fix: bump Go to 1.26.10 and x/text, x/sys in linux-bench-dependency Oct 28, 2026
@figarocorso
figarocorso merged commit 42d7c36 into master Oct 28, 2026
3 checks passed
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.

3 participants