Skip to content

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

Merged
alaudabot merged 1 commit into
alauda-v1.1.0from
fix/go-1264-stdlib-vuln
Jun 8, 2026
Merged

chore(go): rebuild with Go 1.26.4 to fix stdlib CVEs#21
alaudabot merged 1 commit into
alauda-v1.1.0from
fix/go-1264-stdlib-vuln

Conversation

@l-qing

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

Copy link
Copy Markdown

Why

Binaries on `alauda-v1.1.0` build with Go 1.26.3 and carry three stdlib CVEs:

CVE Severity Fixed in
CVE-2026-42504 HIGH Go 1.26.4
CVE-2026-27145 MEDIUM Go 1.26.4
CVE-2026-42507 MEDIUM Go 1.26.4

The git-init binary produced here is consumed downstream by AlaudaDevops/catalog (git-init image), which fails its Trivy gate because of these stdlib CVEs.

What

Bump the go directive in image/git-init/go.mod from 1.26.3 to 1.26.4.

The Alauda release workflow (reusable-release-alauda.yaml) uses actions/setup-go with go-version-file: image/git-init/go.mod, so bumping this directive is sufficient — the next auto-cut -alauda-N release will build on Go 1.26.4 and scan clean.

Files changed

  • image/git-init/go.mod: go 1.26.3go 1.26.4

Rebuild released binaries with Go 1.26.4 to clear stdlib CVE-2026-42504,
CVE-2026-27145 and CVE-2026-42507 (all fixed in Go 1.26.4). The Alauda
release workflow uses setup-go with go-version-file: image/git-init/go.mod,
so bumping this directive is sufficient for the next -alauda-N release to
build on Go 1.26.4 and scan clean downstream in AlaudaDevops/catalog.
@alaudabot alaudabot merged commit bd98692 into alauda-v1.1.0 Jun 8, 2026
1 check passed
@alaudabot alaudabot deleted the fix/go-1264-stdlib-vuln branch June 8, 2026 01:52
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