Skip to content

fix: upgrade golang.org/x/crypto to v0.56.0 - #3404

Closed
chainloop-platform[bot] wants to merge 1 commit into
mainfrom
chainloop/fix-go-2026-6354-golang-org-x-crypto-20260904-213354
Closed

chainloop-platform[bot] wants to merge 1 commit into
mainfrom
chainloop/fix-go-2026-6354-golang-org-x-crypto-20260904-213354

Conversation

@chainloop-platform

@chainloop-platform chainloop-platform Bot commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Bump golang.org/x/crypto from v0.55.0 to v0.56.0 so the repository no longer pins the vulnerable module version flagged by GO-2026-6354-golang.org/x/crypto. This is the minimal manifest-only remediation for the scanner finding.

Vulnerability Fixed

GO-2026-6354-golang.org/x/crypto (HIGH): golang.org/x/crypto/ssh could deadlock an SSH connection when a malicious peer floods requests before a channel is established.

Changes Made

  • Updated golang.org/x/crypto in go.mod from v0.55.0 to v0.56.0, the first fixed release identified by the assessment hint and verified with go list -m -json golang.org/x/crypto@v0.56.0.
  • Added the corresponding v0.56.0 checksums to go.sum so the patched module version is recorded for reproducible resolution.

Verification

Ran syft dir:. -o cyclonedx-json=/workspace/run/out/sbom.json && grype sbom:/workspace/run/out/sbom.json --only-fixed -o json against /workspace/run/repo. Outcome: resolved — grype did not report GO-2026-6354-golang.org/x/crypto in the patched SBOM.

Risk Assessment

View the risk assessment in Chainloop

Review in cubic

@matiasinsaurralde

Copy link
Copy Markdown
Contributor

Fixed in #3403

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant