Update all packages with golang.org/x/crypto to v0.45.0#296
Merged
Conversation
johanbrandhorst
approved these changes
Dec 1, 2025
Contributor
johanbrandhorst
left a comment
johanbrandhorst
left a comment
There was a problem hiding this comment.
Thanks, seems reasonable to me!
sgmiller
approved these changes
Dec 1, 2025
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
3 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.
Update all packages that had a direct or indirect dependency on golang.org/x/crypto to version v0.45.0 to remediate various warnings from the package. This latest version of golang.org/x/crypto, requires Go 1.24 so various packages have had their minimum Go versions bumped. I've also bumped the versions we run within CI accordingly to 1.25 and 1.24 from 1.24 and 1.23.
To the best of my knowledge none of the packages use any of the code that was part of the reported vulnerabilities but this will help lower the number of false positives.
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.