fix: upgrade Go toolchain to 1.22 to address CVE-2025-22871, CVE-2025-68121, CVE-2024-3566#160
Open
ethan-wispr wants to merge 1 commit into
Open
Conversation
|
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
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.
Fixes #159.
Why
All published
app-builder-binbinaries are compiled withgo1.21.13, which is affected by three high/critical CVEs:net/http: request smuggling via malformed chunked encodingnet/http: arbitrary code execution via HTTP/2 CONTINUATION framescmd/go: argument injection on WindowsAll three are fixed in Go 1.22+. Security scanners (e.g. Syft/Grype) flag every project that depends on
app-builder-bin, blocking SBOM audits even though the exposure is build-time rather than runtime.What Changed
.github/actions/setup/action.yml:go-version: '1.21'→'1.22'go.mod:go 1.21→go 1.22No source changes required. Go 1.22 is backwards-compatible with this codebase — the only language behaviour change relevant to existing code (range loop variable scoping) doesn't apply here.
Testing
CI runs
make testandmake build-all, which cross-compiles for all 11 target platforms. That's the right validation gate for this change.