security: vulnerability remediation - #58
Open
kernel-internal[bot] wants to merge 1 commit into
Open
Conversation
Remediates GHSA-rg2x-37c3-w2rh (CVE-2026-42306, high): a race in docker cp mount setup lets a malicious container redirect a bind mount to an arbitrary host path. The advisory lists no patched version for github.com/docker/docker; the module stops at v28.5.2 and the fix only exists under the renamed github.com/moby/moby/v2 path. Upgrading go-containerregistry 0.20.7 -> 0.21.7 drops the docker/docker requirement entirely in favour of moby/moby/api and moby/moby/client, so none of the affected code is compiled in any more (verified with go list -deps). 0.21.7 also requires docker/cli v29.5.3, so the replace directive pinning cli to v29.2.0 is no longer needed and has been removed. docker/docker v28.5.2 still appears in the module graph via kernel/hypeman-go v0.20.0, which is the latest release; clearing that needs a hypeman-go release and is tracked separately. Co-authored-by: Cursor <[email protected]>
ulziibay-kernel
force-pushed
the
security/vuln-remediation
branch
from
July 31, 2026 18:07
59bcdee to
e35dc68
Compare
ulziibay-kernel
approved these changes
Jul 31, 2026
ulziibay-kernel
left a comment
ulziibay-kernel
left a comment
Contributor
There was a problem hiding this comment.
Replaced the original pseudo-version pin, which moved out of the scanner's vulnerable range without containing the docker cp fix, with an upgrade to go-containerregistry 0.21.7. That drops github.com/docker/docker from the graph in favour of moby/moby/client; go list -deps confirms none of the affected code is linked. CI green.
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.
Vulnerability Remediation
Fixed
Not Included
Deferred details
Note
Medium Risk
Touches the dependency chain used by
push(go-containerregistry/remote/daemon); behavior should be unchanged but container registry auth and push warrant a quick smoke test.Overview
Security-focused dependency refresh for container image push/pull paths (GHSA-rg2x-37c3-w2rh). No application source changes—only
go.mod/go.sum.Bumps
github.com/google/go-containerregistryfrom v0.20.7 to v0.21.7, which pulls in a newer Docker/Moby client stack instead of pinninggithub.com/docker/dockerdirectly. Thereplaceongithub.com/docker/cliis removed; indirect deps move togithub.com/docker/cliv29.5.3,moby/moby/apiandmoby/moby/client, and drop several older Docker/grpc/protobuf transitive modules.golang.org/x/sysand OpenTelemetry-related indirect versions are updated alongside routine lockfile churn.Reviewed by Cursor Bugbot for commit e35dc68. Bugbot is set up for automated code reviews on this repo. Configure here.