build: Update module golang.org/x/crypto to v0.56.0 [SECURITY] (releases/v5.x) by go-git-renovate[bot] · Pull Request #2357 · go-git/go-git · GitHub
Skip to content

build: Update module golang.org/x/crypto to v0.56.0 [SECURITY] (releases/v5.x) - #2357

Open
go-git-renovate[bot] wants to merge 1 commit into
releases/v5.xfrom
renovate/releases/v5.x-go-golang.org-x-crypto-vulnerability
Open

build: Update module golang.org/x/crypto to v0.56.0 [SECURITY] (releases/v5.x)#2357
go-git-renovate[bot] wants to merge 1 commit into
releases/v5.xfrom
renovate/releases/v5.x-go-golang.org-x-crypto-vulnerability

Conversation

@go-git-renovate

@go-git-renovate go-git-renovate Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
golang.org/x/crypto v0.55.0v0.56.0 age confidence

Prevent DoS on deadlocked undecided channel in golang.org/x/crypto/ssh

CVE-2026-78662 / GO-2026-6354

More information

Details

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection.

Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Prevent DoS on deadlocked established channel in golang.org/x/crypto/ssh

CVE-2026-56855 / GO-2026-6355

More information

Details

Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection.

Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@go-git-renovate go-git-renovate Bot added the dependencies Pull requests that update a dependency file label Sep 3, 2026
@go-git-renovate

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: cli/go-git/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.25.0 -> 1.26.0
File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.25.0 -> 1.26.0

@go-git-renovate
go-git-renovate Bot force-pushed the renovate/releases/v5.x-go-golang.org-x-crypto-vulnerability branch from 822f3b3 to 3e1e0e0 Compare September 4, 2026 09:19
Signed-off-by: go-git-renovate[bot] <245267575+go-git-renovate[bot]@users.noreply.github.com>
Signed-off-by: go-git-renovate[bot] <245267575+go-git-renovate[bot]@users.noreply.github.com>
@go-git-renovate
go-git-renovate Bot force-pushed the renovate/releases/v5.x-go-golang.org-x-crypto-vulnerability branch from 3e1e0e0 to 9392b67 Compare September 5, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants