Repository navigation
[release-1.20] upgrade to go 1.26.10 to fix CVE-2026-111943 - #1242
Merged
andyzhangx merged 2 commits intoOct 23, 2026
Merged
andyzhangx merged 2 commits into
andyzhangx merged 2 commits into
Conversation
94dd4dae Merge pull request kubernetes-csi#321 from andyzhangx/patch-17 678187e1 upgrade to go 1.26.10 to fix CVE-2026-111943 git-subtree-dir: release-tools git-subtree-split: 94dd4dae3245f7f8a0d731e16a73995e90ad84ff
Signed-off-by: andyzhangx <xiazhang@microsoft.com>
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
andyzhangx
merged commit Oct 23, 2026
aabf299
into
kubernetes-csi:release-1.20
19 of 21 checks passed
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Update
release-1.20, following livenessprobe#465 and csi-release-tools#321, to build with Go 1.26.10 for CVE-2026-111943.csi-driver-smb:release-1.20at8e91007392afe928c15380bbea0a294b144e891d, rechecked before push. This PR targetsrelease-1.20, not master.release-toolsfrom7bacb813921c5b269bc4ba218d518004dda5288eto latest upstream master94dd4dae3245f7f8a0d731e16a73995e90ad84ffusing:CSI_PROW_GO_VERSION_BUILDfrom 1.26.9 to 1.26.10..github/workflows/trivy.yamlGo pin to 1.26.10, so the workflow's locally built scan image uses the updated toolchain too.release-tools/build.makeis preserved byte-for-byte. Its residual diff against upstream is identical before and after the import; all other subtree files match upstream.The release branch already includes preceding release-tools updates, so this PR changes exactly two lines in two files. No driver/runtime code, dependencies, CA packages, or vulnerability ignore entries are modified.
Security context and scope
As described in Go issue #82345 and csi-release-tools#321, CVE-2026-111943 concerns certificate trust in specific CA intermediates. Go's
crypto/x509mitigation filters chains containing the distrusted intermediates out ofCertificate.Verifyresults. The Go security team classified this as URGENT-track.This updates the build toolchain only. Existing binaries and published images must still be rebuilt, published, and deployed; the change does not retroactively patch them. Actual exposure depends on TLS verification paths and trust configuration. Go's compiled standard-library mitigation and updates to OS CA packages/non-Go TLS clients are separate tasks; this PR does not claim that all image or OS-package vulnerabilities are resolved.
Which issue(s) this PR fixes:
Related to kubernetes-csi/csi-release-tools#321 and golang/go#82345.
Special notes for your reviewer:
Validation:
git diff --checkpasses; verified the exact two-line/two-file scope.bash -npasses for all 17 top-levelrelease-tools/*.shscripts.1.26.10.release-tools/build.makeis preserved byte-for-byte. Its residual diff against upstream is identical before and after the import; all other subtree files match upstream.No component/image build, Trivy scan, Windows build, or cluster E2E run was performed locally (Go, Make, and Docker are unavailable).
Does this PR introduce a user-facing change?:
/release-note-none