CVE-2026-39827: golang.org/x/crypto: Invoking memory leak when rejecting channels can lead to DoS
An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connection's internal state and released for garbage collection.
Published Jun 25, 2026 · Updated Jul 7, 2026
Affected packages
golang.org/x/crypto
- Ecosystem
- Go
- Affected
- < 0.52.0
- Fixed in
- 0.52.0
- Check
go list -m golang.org/x/crypto
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connection's internal state and released for garbage collection.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-39828
golang.org/x/crypto vulnerable to invoking bypass of certificate restrictions
medium6.3Jun 25, 2026CVE-2026-39829
golang.org/x/crypto: Invoking pathological RSA/DSA parameters may cause DoS
high7.5Jun 25, 2026CVE-2026-39830
golang.org/x/crypto: Invoking client can cause server deadlock on unexpected responses
critical9.1Jun 25, 2026CVE-2026-39831
golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed
critical9.1Jun 25, 2026CVE-2026-39832
golang.org/x/crypto doesn't drop invoking agent constraints when forwarding keys
critical9.1Jun 25, 2026CVE-2026-39833
golang.org/x/crypto doesn't enforce invoking key constraints
critical9.1Jun 25, 2026
