Authenticated server crash via unreleased rejected channels
Published May 22, 2026 · Updated May 22, 2026
Resource exhaustion in golang.org/x/crypto/ssh before 0.52.0 allows remote authenticated users to crash SSH servers via rejected channels. The channel.Reject path leaves rejected channels in the connection's internal state, so repeated openings retain memory instead of allowing garbage collection. An authenticated SSH client can exhaust server memory and terminate the process, interrupting every connection handled by that server.
Summary
What happened
Resource exhaustion in golang.org/x/crypto/ssh before 0.52.0 allows remote authenticated users to crash SSH servers via rejected channels. The channel.Reject path leaves rejected channels in the connection's internal state, so repeated openings retain memory instead of allowing garbage collection. An authenticated SSH client can exhaust server memory and terminate the process, interrupting every connection handled by that server.
The record
- CVE
- CVE-2026-39827
- Published
- May 22, 2026
- Updated
- May 22, 2026
- Vendor
- golang.org/x/crypto
- Product
- golang.org/x/crypto/ssh
- Classifications
- CWE-924, T1499.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 22, 2026CVE publishedPublication date reported by the CVE source.
- May 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.52.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo