When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
Update golang.org/x/crypto to 0.52.0; golang.org/x/crypto/ssh to 0.52.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scangolang.org/x/crypto/ssh vulnerable to infinite loop on large channel writes affects golang.org/x/crypto (go), golang.org/x/crypto/ssh (go). Severity is critical. When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
AI coding agents often install or upgrade packages automatically in go. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/cryptogo | <0.52.0 | 0.52.0 |
When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
Update golang.org/x/crypto to 0.52.0; golang.org/x/crypto/ssh to 0.52.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scangolang.org/x/crypto/ssh vulnerable to infinite loop on large channel writes affects golang.org/x/crypto (go), golang.org/x/crypto/ssh (go). Severity is critical. When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
AI coding agents often install or upgrade packages automatically in go. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/cryptogo | <0.52.0 | 0.52.0 |
| golang.org/x/crypto/sshgo |
|---|
| <0.52.0 |
| 0.52.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| golang.org/x/crypto/sshgo |
|---|
| <0.52.0 |
| 0.52.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard