CVE-2026-39827
published 2026-05-22CVE-2026-39827: An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server…
PriorityP433medium6.5CVSS 3.1
AVNACLPRLUINSUCNINAH
EPSS
0.20%
9.5th percentile
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.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| golang.org | x_crypto_golang.org_x_crypto_ssh | < 0.52.0 | 0.52.0 |
| golang.org | x_crypto_ssh | >= 0 < 0.52.0 | 0.52.0 |
| golang | crypto | < 0.52.0 | 0.52.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
golang.org/x/crypto/ssh: Invoking memory leak when rejecting channels can lead to DoS
ghsa·2026-06-25
CVE-2026-39827 [MEDIUM] CWE-924 golang.org/x/crypto/ssh: Invoking memory leak when rejecting channels can lead to DoS
golang.org/x/crypto/ssh: 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.
VulDB
x-crypto up to 0.51.x memory leak (EUVD-2026-31392)
vuldb·2026-05-23
CVE-2026-39827 [LOW] x-crypto up to 0.51.x memory leak (EUVD-2026-31392)
A vulnerability identified as problematic has been detected in x-crypto up to 0.51.x. The affected element is an unknown function. The manipulation leads to memory leak.
This vulnerability is traded as CVE-2026-39827. It is possible to initiate the attack remotely. There is no exploit available.
You should upgrade the affected component.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-05-22
Published