Bump golang.org/x/crypto to v0.56.0 for two CVEs - #239
Merged
Conversation
Contributor
sduchesneau
requested review from
UlysseCorbeil
and removed request for
billettc
September 3, 2026 17:47
UlysseCorbeil
approved these changes
Sep 3, 2026
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
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.
The Docker Scout step of the
Build docker imageworkflow now fails ondevelop:golang.org/x/cryptov0.55.0 carries CVE-2026-78662 and CVE-2026-56855, both HIGH, both fixed in v0.56.0. The image itself builds and pushes; only the scan gate fails.Dependabot will not open this one on its own: neither CVE is in the GitHub Advisory Database yet (Docker Scout uses its own feed), so there is no alert to raise a security update from, and
x/cryptois an indirect dependency, which the weekly grouped version-update PR does not cover.One-line bump of the indirect requirement, nothing else changes.