Skip to content

fix(security/unknown/): update module golang.org/x/crypto to v0.56.0 [security] (main) - #7846

Open
renovate-sh-app[bot] wants to merge 1 commit into
mainfrom
renovate/main-security-golang.orgxcrypto
Open

renovate-sh-app[bot] wants to merge 1 commit into
mainfrom
renovate/main-security-golang.orgxcrypto

Conversation

@renovate-sh-app

@renovate-sh-app renovate-sh-app Bot commented Sep 2, 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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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


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

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

…[security]

| datasource | package             | from    | to      |
| ---------- | ------------------- | ------- | ------- |
| go         | golang.org/x/crypto | v0.55.0 | v0.56.0 |


Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
@tempo-ci-app

tempo-ci-app Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🤖 fix-renovate-prs rerun_failed_actions: The single failing check is TestCompactionProvider_EmptyStart in modules/backendscheduler/provider, which is unrelated to this crypto vendor bump and has a documented flakiness history (deflaked in #7629); it passes cleanly locally against this branch, so a rerun should clear it.

@tempo-ci-app

tempo-ci-app Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🤖 fix-renovate-prs rerun_failed_actions: The only failure is TestCompactionProvider_EmptyStart in modules/backendscheduler/provider — a known flaky test (already deflaked once in 9a659d3) with no path to the golang.org/x/crypto v0.55→v0.56 bump this PR ships, and it passes 5/5 locally, so a rerun should clear it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge-security-update dependencies Pull requests that update a dependency file gomod minor renovate Applied to PR's created by renovatebot severity:UNKNOWN update-minor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants