Repository navigation
fix: bump golang.org/x/crypto to v0.56.0 - #3403
Merged
matiasinsaurralde merged 1 commit intoSep 4, 2026
Merged
matiasinsaurralde merged 1 commit into
matiasinsaurralde merged 1 commit into
Conversation
…olang.org/x/crypto
matiasinsaurralde
self-requested a review
September 4, 2026 23:07
matiasinsaurralde
deleted the
chainloop/fix-go-2026-6355-golang-org-x-crypto-20260904-213324
branch
September 4, 2026 23:07
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
Updated
golang.org/x/cryptofromv0.55.0tov0.56.0, the first fixed release for GO-2026-6355-golang.org/x/crypto. This keeps the dependency tree on the patched SSH implementation and removes the reported finding from the repository SBOM scan.Vulnerability Fixed
GO-2026-6355-golang.org/x/crypto, severity HIGH. A malicious SSH peer could send crafted channel or global-request messages after channel establishment and deadlock the connection instead of failing closed.
Changes Made
golang.org/x/cryptoingo.modfromv0.55.0tov0.56.0, the fixed release identified by the assessment hint.go.sumentries so the module checksum matches the patched release.Verification
Ran
syft dir:. -o cyclonedx-json=/workspace/run/sbom.json && grype sbom:/workspace/run/sbom.json --only-fixed -o jsonagainst the patched repository. Outcome:resolved— grype no longer reportsGO-2026-6355-golang.org/x/cryptoin the generated SBOM for the updated dependency set.Risk Assessment
View the risk assessment in Chainloop