CVE-2026-78662: Prevent DoS on deadlocked undecided channel in golang.org/x/crypto/ssh

Published Sep 2, 2026
·
Updated

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

Other sources

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.

— MITRE

Affected Software

17 affected componentsFixes available
golang.org/x/crypto/ssh=
Golang Crypto Go<0.56.0
Microsoft azl3 packer 1.9.5-20<1.9.5-21
1.9.5-21
Microsoft azl3 docker-compose 2.27.0-13<2.27.0-14
2.27.0-14
Microsoft azl3 gh 2.98.0-1<2.101.0-1
2.101.0-1
Microsoft azl3 cf-cli 8.7.11-8<8.7.11-9
8.7.11-9
Microsoft azl3 cert-manager 1.12.15-12<1.12.15-14
1.12.15-14
Microsoft azl3 docker-buildx 0.14.0-16<0.14.0-17
0.14.0-17
Microsoft azl3 telegraf 1.31.0-31<1.31.0-33
1.31.0-33
Microsoft azl3 kubernetes 1.30.10-29<1.30.10-30
1.30.10-30
Microsoft azl3 kubevirt 1.8.4-1<1.8.4-2
1.8.4-2
Microsoft azl3 packer 1.9.5-21<1.9.5-21
1.9.5-21
Microsoft azl3 docker-compose 2.27.0-14<2.27.0-14
2.27.0-14
Microsoft azl3 cf-cli 8.7.11-9<8.7.11-9
8.7.11-9
Microsoft azl3 kubernetes 1.30.10-30<1.30.10-30
1.30.10-30
Microsoft azl3 kubevirt 1.8.4-2<1.8.4-2
1.8.4-2
Microsoft azl3 docker-buildx 0.14.0-17<0.14.0-17
0.14.0-17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.9.5-21
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.27.0-14
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.101.0-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.7.11-9
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.12.15-14
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.14.0-17
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.31.0-33
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.30.10-30
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.8.4-2

Event History

Sep 2, 2026
CVE Published
via MITRE·07:37 PM
Data Sourced
via MITRE·07:37 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 5, 2026
Data Sourced
via Microsoft·08:38 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:38 AM
Affected Software
Updated
via Microsoft·08:38 AM
DescriptionSeverity

Frequently Asked Questions

1

Who can trigger the denial of service?

A malicious SSH peer can trigger it by flooding incoming channel requests while a channel is registered but not yet established. The resulting deadlock can affect the entire SSH connection.

2

What traffic is accepted before a channel is established after the fix?

Before establishment, packet handling accepts only channel open confirmation or open failure packets. Other packets are dropped without blocking or tearing down the connection.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203