CVE-2026-39830: Invoking client can cause server deadlock on unexpected responses in golang.org/x/crypto/ssh
A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. The blocked goroutine could not be released by calling Close(), resulting in a resource leak per connection. Unsolicited global responses are now discarded.
Security readout for executives and security teams
Plain-English summary
A malicious SSH server can cause a Go application using the affected SSH client library to stop processing a connection and retain resources. Repeated connections could degrade or exhaust service capacity. The supplied record rates this critical, but the affected-version data is incomplete, so organizations must confirm exposure against the Go advisory.
Executive priority
Treat confirmed exposure as an urgent availability risk, especially for services making many outbound SSH connections or reaching untrusted peers. Prioritize dependency inventory immediately, then patch and redeploy confirmed affected applications. Do not claim compromise solely from resource growth; investigate telemetry and connection destinations.
Technical view
Unsolicited SSH global-request responses can fill an internal buffer and block the connection read loop. Calling Close() does not release the blocked goroutine, producing a per-connection resource leak and potential deadlock. The corrected behavior discards unsolicited global responses. The record maps this to CWE-772 and CWE-833.
Likely exposure
Potentially exposed systems are Go applications using golang.org/x/crypto/ssh as an SSH client and connecting to malicious or untrusted SSH peers. Internet reachability increases opportunity but is not required. The supplied version entry is ambiguous and defaults to unaffected, so it cannot establish which deployed versions are vulnerable.
Exploitation context
The condition is remotely triggerable by a malicious SSH peer without privileges or user interaction, according to the supplied CVSS vector. No CISA KEV listing or other supplied evidence establishes active exploitation. The bundle also provides no evidence of public weaponization or observed attacks.
Researcher notes
The documented impact is a blocked read loop and unreleasable goroutine per malicious connection. Although the supplied CVSS includes high confidentiality impact, the narrative evidence describes resource exhaustion and availability loss, not a data-disclosure mechanism. Exact vulnerable and fixed versions are absent from the bundle; consult the linked Go advisory before drawing version conclusions.
Mitigation direction
Check GO-2026-5017 and the Go announcement for affected and corrected versions.
Update golang.org/x/crypto/ssh to the vendor-designated corrected release.
Rebuild and redeploy applications that statically include the affected dependency.
Apply relevant Red Hat errata where the dependency comes from supported Red Hat packages.
Restrict SSH client connections to trusted destinations until remediation is verified.
Validation and detection
Inventory applications and binaries containing golang.org/x/crypto/ssh.
Compare resolved dependency versions with the Go vulnerability advisory.
Confirm rebuilt artifacts contain the corrected library version.
Exercise SSH connection cleanup defensively in staging and check for retained goroutines.
Monitor connection counts, goroutines, memory, and service availability for unexplained growth.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-772: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-772 · source CWE mapping
Missing Release of Resource after Effective Lifetime
Missing Release of Resource after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.