Fix possible fix(deps): golang.org/x/crypto v0.53.0 → 0.55.0 (CVE-2026-56854) in go.mod - #8
Merged
xiaozhou26 merged 1 commit intoSep 3, 2026
Conversation
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
2 participants
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.
This changes
go.modto address something a scan flagged. It is around line 1.CVE-2026-56854 reveals that source-address restrictions configured via several SSH authentication callbacks (e.g., PasswordCallback, KeyboardInteractiveCallback) are silently ignored. This flaw allows attackers to bypass IP-based access controls, potentially granting unauthorized remote access. Due to the critical severity and direct impact on authentication security, immediate remediation is required.
Update golang.org/x/crypto to v0.55.0 to address CVE‑2026‑56854.
For reference: rule
CVE-2026-56854. Rated critical.Take or leave whichever parts are useful. If this is not the right approach, closing is fine.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.