Skip to content

Bump golang.org/x/crypto to v0.55.0 - #55

Open
carrotRakko wants to merge 1 commit into
superfly:mainfrom
carrotRakko:bump-x-crypto-v0.55.0
Open

Bump golang.org/x/crypto to v0.55.0#55
carrotRakko wants to merge 1 commit into
superfly:mainfrom
carrotRakko:bump-x-crypto-v0.55.0

Conversation

@carrotRakko

Copy link
Copy Markdown

Bumps golang.org/x/crypto from v0.50.0 to v0.55.0 (go get golang.org/x/crypto@v0.55.0 && go mod tidy; golang.org/x/sys v0.43.0 → v0.47.0 and golang.org/x/text v0.36.0 → v0.41.0 move as transitive requirements).

Why: v0.55.0 carries the fix for CVE-2026-56854 / GO-2026-6303 in golang.org/x/crypto/ssh (the source-address critical option was not enforced for Permissions returned by non-public-key auth callbacks). tokenizer itself only imports curve25519 and nacl/box, so the vulnerable ssh server path is not linked into the binary — but container scanners (AWS Inspector in our case) flag the module version recorded in the binary's build info, so every image built from this module currently shows up as HIGH. Bumping clears that and keeps the dependency current, same as #50 did for the previous round.

Verification: go build ./... and go test ./... pass locally (go 1.26, linux/arm64).


This PR was prepared by Claude Code (an AI coding agent) and reviewed and approved by a human (@carrotRakko) before submission.

✍️ Author: Claude Code with @carrotRakko (AI-written, human-approved)

Picks up the fix for CVE-2026-56854 (GO-2026-6303) in golang.org/x/crypto/ssh.
tokenizer only imports curve25519 and nacl/box, so the vulnerable ssh server
code path is not linked into the binary; the bump clears scanner findings
(AWS Inspector flags the module version) and keeps the dependency current.

`go get golang.org/x/crypto@v0.55.0 && go mod tidy`; golang.org/x/sys and
golang.org/x/text move as transitive requirements. `go build ./...` and
`go test ./...` pass.
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