Skip to content

Bump golang.org/x/crypto to v0.55.0 (CVE-2026-56854) - #38

Merged
LouisLotter merged 1 commit into
mainfrom
cve-x-crypto-ssh-0-55-0
Aug 30, 2026
Merged

Bump golang.org/x/crypto to v0.55.0 (CVE-2026-56854)#38
LouisLotter merged 1 commit into
mainfrom
cve-x-crypto-ssh-0-55-0

Conversation

@ai-collaboration-app

Copy link
Copy Markdown

Clears the HIGH finding CVE-2026-56854 / GO-2026-6303 (source-address critical option not enforced for non-public-key auth callbacks in golang.org/x/crypto/ssh), which has no fix below v0.55.0.

golang.org/x/crypto/ssh is not in this repo's build graph — go list -deps ./... links only golang.org/x/crypto/sha3 — so the advisory is not reachable. Grype still reports it because it matches Go advisories against the binary's embedded module list rather than linked packages, so the bump is what clears it on the published assets.

The golang.org/x/{net,sys,term,text} bumps are what the module graph requires to resolve v0.55.0. All remain indirect; no direct dependency or Go version changes.

CVE ticket: https://github.com/StackVista/cve-reporter/issues/57
Finding revision: sha256:e926258a2ef22a892e629f2143d9fc788f191bc85c96d214073d0c5891bd6170
Finding key addressed: sha256:5c4649d7afedf705e1352338f62917c80f464cd5928eec0acbeddfcd42a9f985

GO-2026-5932 (openpgp) is unaffected by this change and stays open on the ticket — it has no fixed version in any release.

CVE-2026-56854 (GO-2026-6303) has no fix below v0.55.0, and Grype matches Go
advisories against the binary's embedded module list regardless of which
packages are linked, so the published assets report it even though
golang.org/x/crypto/ssh is absent from the build graph.

The coupled golang.org/x sibling bumps are what the module graph requires to
resolve v0.55.0; no direct dependency or Go version changes.

Co-authored-by: Cve Ticket Reconciler <cve-ticket-reconciler@stackstate.invalid>
@LouisLotter
LouisLotter merged commit 8ff3aef into main Aug 30, 2026
6 checks passed
@LouisLotter
LouisLotter deleted the cve-x-crypto-ssh-0-55-0 branch August 30, 2026 06:06
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.

2 participants