7.5
Élevée
CVE-2026-56855 Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the…
Description
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| golang.org/x/crypto/ssh 0.56 | premières → < 0.56.0 | 0.56.0 |
Références
- go.dev go.dev
- go.dev go.dev
- groups.google.com groups.google.com
- pkg.go.dev pkg.go.dev
Chronologie
- Publiée
- Dernière modification
Autres CVE de golang.org/x/crypto/ssh
Les 15 CVE de golang.org/x/crypto/ssh →
CVE-2026-78662
Previously, a channel registered in the mux's chanList is not usable until it is established
7.5
Élevée
CVE-2026-56854
The source-address critical option in the Permissions returned by an authentication callback was only enforced for the…
7.5
Élevée
CVE-2026-39827
An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory…
6.5
Moyenne
CVE-2026-39834
When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal…
9.1
Critique