Invoking memory leak when rejecting channels can lead to DoS in golang.org/x/crypto/ssh
cve-program · CVE-2026-39827
PublishedAn 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.
Read the publisher's advisoryeuvd · EUVD-2026-31392
PublishedAn 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.
Read the publisher's advisorynvd · CVE-2026-39827
PublishedAn 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.
Read the publisher's advisoryosv · GHSA-qpw4-5x99-6vjp
PublishedAn 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.
Read the publisher's advisoryosv · GO-2026-5016
PublishedAn 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-39827 · CVE overview and exploitation status
cve-program · CVE-2026-39827
- https://go.dev/issue/35127
- https://go.dev/cl/781320
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5016
euvd · EUVD-2026-31392
- https://go.dev/issue/35127
- https://go.dev/cl/781320
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5016
nvd · CVE-2026-39827
- https://go.dev/cl/781320
- https://go.dev/issue/35127
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5016
osv · GHSA-qpw4-5x99-6vjp
- https://nvd.nist.gov/vuln/detail/CVE-2026-39827
- https://cs.opensource.google/go/x/crypto
- https://go.dev/cl/781320
- https://go.dev/issue/35127
- https://groups.google.com/g/golang-announce/c/a082jnz-LvI
- https://pkg.go.dev/vuln/GO-2026-5016
osv · GO-2026-5016
Related changes
Linked by CVE identifierNo related changes are available here.