build(deps): bump x/crypto, x/net, and go-git for security fixes#2641
Merged
Conversation
Bumps the security-relevant Go modules in isolation, split out of the dependabot go-dependencies group (#2640) so the critical/high CVE fixes can land without the moby/docker and go-containerregistry bumps that are currently breaking acceptance tests: - golang.org/x/crypto 0.51.0 -> 0.53.0 (GO-2026-5005/5006/5013-5023/5033) - golang.org/x/net 0.53.0 -> 0.55.0 (GO-2026-5025-5030) - github.com/go-git/go-git/v5 5.19.0 -> 5.19.1 (GHSA-crhj-59gh-8x96, GHSA-m7cr-m3pv-hgrp, GHSA-w5pp-99ch-qj29) x/sync, x/sys, x/term, and x/text move forward transitively via x/crypto. The moby/moby/client 0.5.0 + moby/moby/api 1.55.0 + docker/cli + go-containerregistry 0.21.7 bumps from the group are intentionally held: the daemon client jump is ahead of imgutil (pinned to moby/moby/client 0.2.x) and breaks daemon rebase, and ggcr 0.21.7 breaks manifest annotate. None of those resolve a fixable CVE. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Signed-off-by: Juan Bustamante <[email protected]>
github-actions
Bot
added
the
type/chore
This was referenced Jun 23, 2026
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
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
1 participant
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
Bumps the security-relevant Go modules in isolation, split out of the dependabot go-dependencies group (#2640) so the critical/high CVE fixes can land now. The remaining bumps in #2640 (
moby/moby/client0.5.0,moby/moby/api1.55.0,docker/cli,go-containerregistry0.21.7) are intentionally not included here — see below.golang.org/x/crypto0.51.0 → 0.53.0 — GO-2026-5005/5006/5013/5014/5015/5016/5017/5018/5019/5020/5021/5023/5033 (5 critical)golang.org/x/net0.53.0 → 0.55.0 — GO-2026-5025/5027/5028/5029/5030 (1 critical)github.com/go-git/go-git/v55.19.0 → 5.19.1 — GHSA-crhj-59gh-8x96, GHSA-m7cr-m3pv-hgrp, GHSA-w5pp-99ch-qj29 (supersedes build(deps): bump github.com/go-git/go-git/v5 from 5.19.0 to 5.19.1 #2607)x/sync,x/sys,x/term, andx/textmove forward transitively viax/crypto.Why split from #2640
The group bump fails acceptance on two reproducible regressions that buy no fixable CVE:
moby/moby/client0.5.0 /moby/moby/api1.55.0 break daemon rebase (rebase app image: could not find base layer in image). The daemon client jump is ahead of imgutil, which is still pinned tomoby/moby/client0.2.x even on its main branch — daemon top-layer detection breaks.docker/docker's open CVEs have no fixed version yet, anddocker/cli29.4.3 already satisfies GO-2026-4610, so there is no CVE benefit to forcing these.go-containerregistry0.21.7 breaksmanifest annotateacceptance.Both should land later once imgutil supports
moby/moby/client0.5.0.Output
Before
After
Documentation
Related
Supersedes #2607. Splits out the safe portion of #2640.