Skip to content

chore(go): rebuild with Go 1.26.4 to fix stdlib CVEs#49

Merged
l-qing merged 3 commits into
alauda-v1.42.3from
fix/go-1264-stdlib-vuln
Jun 8, 2026
Merged

chore(go): rebuild with Go 1.26.4 to fix stdlib CVEs#49
l-qing merged 3 commits into
alauda-v1.42.3from
fix/go-1264-stdlib-vuln

Conversation

@l-qing
Copy link
Copy Markdown

@l-qing l-qing commented Jun 7, 2026

Why

Released binaries on alauda-v1.42.3 build with Go 1.26.3 and carry stdlib
CVE-2026-42504 (HIGH), CVE-2026-27145 (MEDIUM) and CVE-2026-42507
(MEDIUM), all fixed in Go 1.26.4.

What

Bump the go directive in go.mod to 1.26.4. The Alauda release
workflow uses actions/setup-go with go-version-file: go.mod, so the
next auto-cut -alauda-N release builds on Go 1.26.4 and scans clean.

Consumed downstream by AlaudaDevops/catalog images.

l-qing and others added 3 commits June 7, 2026 16:34
Rebuild released binaries with Go 1.26.4 to clear stdlib CVE-2026-42504,
CVE-2026-27145 and CVE-2026-42507. The Alauda release workflow resolves the
toolchain via setup-go go-version-file: go.mod, so bumping this directive is
sufficient for the next -alauda-N release to build on Go 1.26.4.
The Build-Snapshot-Artifacts job was stuck queued for ~50min waiting on
an ephemeral runs-on runner. Re-trigger to requeue a fresh provisioning.
@l-qing l-qing merged commit 6268ac2 into alauda-v1.42.3 Jun 8, 2026
5 of 10 checks passed
@l-qing l-qing deleted the fix/go-1264-stdlib-vuln branch June 8, 2026 01:49
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