Repository navigation
build: release with Go 1.26.10 for CVE-2026-111943 - #206
Merged
Merged
Conversation
tbarbugli
requested review from
JimmyPettersson85,
darkoatanasovski and
yaziine
as code owners
November 1, 2026 11:51
darkoatanasovski
previously approved these changes
Nov 1, 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
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.
Summary
Release binaries were built with Go 1.22, which lacks the crypto/x509 denylist for the compromised eMudhra intermediates (CVE-2026-111943, GO-2026-6809). On Linux, Go verifies against the distro root store without revocation checks, so shipped
stream-clibinaries could accept forged certificates for the Stream API and leak the API secret.Pins the release workflow to Go 1.26.10 (exact patch, so setup-go can't fall back to an older cached 1.26.x).
go.modstays at 1.23 to keep golangci-lint v1.55 in Lint/Reviewdog working.Rollout
Merge, then cut a patch release (v1.10.2) via "Create release PR".