Repository navigation
Bump Go to 1.26.10 to patch GO-2026-6809 - #446
Merged
Merged
Conversation
Go 1.26.10 fixes the crypto/x509 compromised intermediate certificates issue (GO-2026-6809). Matches the bump already shipped in opslevel-agent. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
archf
approved these changes
Nov 2, 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
src/go.modfromgo 1.26.9togo 1.26.10. That patches the crypto/x509 compromised intermediate certificates issue (GO-2026-6809).public.ecr.aws/opslevel/cli:latestimage was built with go1.26.9, whichgo version -mon the binary confirms.src/go.mod(go-version-file), so release builds will use 1.26.10.Note on the image's CA bundle
This PR doesn't change the Docker image. The image is built on
ubuntu:nobleand installsca-certificatesat build time. The published image still trusts all four emSign roots. A new build would pick up Ubuntu's current package, which drops ECC G3 but still trusts C1, ECC C3 and G1. Trust-store scanners may keep flagging those until Ubuntu removes them.Test plan
go mod tidyproduces no other changesgo build ./...andgo vet ./...pass on go1.26.10go test ./...passes except./e2e, which needs live API credentials and fails the same way onmainwith go1.26.9 (401 Unauthorized)task cipasses🤖 Generated with Claude Code