chore(go): rebuild with Go 1.26.4 to fix stdlib CVEs#44
Merged
Conversation
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.
Dockerfile and test/fakeoidc/go.mod were still pinned to 1.26.3 while the main go.mod already requires go >= 1.26.4. With GOTOOLCHAIN=local this caused builds to fail. Bump both to 1.26.4 to restore consistency.
The in-toto-golang v0.11.0 security bump deprecated the legacy Statement/StatementHeader/Subject/ProvenancePredicate types in favor of the protobuf-generated in_toto Attestation Framework v1 API. The attestation code still uses the legacy API, so staticcheck SA1019 fails the lint job. Migrating to the v1 API is a separate effort; mirror the existing Rekor-v1 SA1019 exclusions and suppress the deprecation lint on the affected files until that migration lands.
Two more files under cmd/cosign/cli still use the deprecated in_toto.Statement/StatementHeader API and were missed by the first exclusion pass. Cover them so the lint job passes.
yuzichen12123
approved these changes
Jun 8, 2026
alaudabot
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Released binaries on
alauda-v2.6.2build with Go 1.26.3 and carry stdlibCVE-2026-42504 (HIGH), CVE-2026-27145 (MEDIUM) and CVE-2026-42507
(MEDIUM), all fixed in Go 1.26.4.
What
Bump the
godirective ingo.modto1.26.4. The Alauda releaseworkflow uses
actions/setup-gowithgo-version-file: go.mod, so thenext auto-cut
-alauda-Nrelease builds on Go 1.26.4 and scans clean.Consumed downstream by AlaudaDevops/catalog images.