fix(security/unknown/tools): update module golang.org/x/crypto to v0.56.0 [security] (release-v3.0)

[renovate-sh-app]

This PR contains the following updates:

Package	Change	Age	Confidence
golang.org/x/crypto	v0.52.0 → v0.56.0

---

Warning

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

---

Source-address critical option not enforced for non-public-key auth callbacks in golang.org/x/crypto/ssh

CVE-2026-56854 / GO-2026-6303

More information

Details

The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, and GSSAPIWithMICConfig.AllowLogin callbacks were not validated against the client's remote address, so a source-address restriction set by those callbacks was silently ignored. The check is now applied to the Permissions returned by any authentication callback.

Severity

Unknown

References

• https://go.dev/issue/80213
• https://go.dev/cl/797040

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

---

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

• https://go.dev/issue/81316
• https://go.dev/cl/826504
• https://groups.google.com/g/golang-announce/c/1y3fb2np35U

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

• https://go.dev/issue/81317
• https://go.dev/cl/826524
• https://groups.google.com/g/golang-announce/c/1y3fb2np35U

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.

[renovate-sh-app]

ℹ️ Artifact update notice

File name: tools/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):

• 2 additional dependencies were updated

Details:

Package	Change
golang.org/x/term	v0.43.0 -> v0.45.0
golang.org/x/text	v0.39.0 -> v0.41.0

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: The PR bumps golang.org/x/crypto only inside the separate tools/ module (tools/go.mod, tools/go.sum) — it has no effect on tempo's main module, so the failing tests cannot be caused by this diff. Both failures show flaky signatures unrelated to the bump: TestWorker fails only in TempDir RemoveAll cleanup (async goroutine still writing after test end), TestPushTracesSkipMetricsGenerationIngestStorage is a Kafka header-assertion flake, and the e2e-storage run reported 91 failures in 1500s driven by tempodb_compaction_outstanding_blocks/blocklist_length metric-timing races — rerun the failed actions.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: The only failure is a flaky TempDir cleanup race in modules/backendworker TestWorker ("TempDir RemoveAll cleanup: … directory not empty"); the test body itself passed and the PR only bumps tools/go.mod deps, so nothing in modules/backendworker is exercised by this diff. Rerun the failed job.