When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
CVE-2026-39834
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EPSS
- 37.4%
- KEV
- Not listed
Published
May 22, 2026
Last Modified
May 28, 2026
Advisory Details (4)
Auto-updated May 28, 2026x/crypto/ssh: infinite loop on large channel writes · Issue #79567 · golang/go · GitHub
https://go.dev/issue/79567Vendor Advisories for CVE-2026-39834(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:37387Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update
- GHSA-rm3j-f69w-wqmqGitHub Security AdvisoriesCritical
golang.org/x/crypto vulnerable to infinite loop on large channel writes
- CVE-2026-39834Microsoft Security Response Center (MSRC)High
Invoking infinite loop on large channel writes in golang.org/x/crypto/ssh
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | lxd-tools (2.0.11-0ubuntu1~16.04.4+esm3) @ xenial | 2026-06-29 | ubuntu |
| ubuntu | google-guest-agent (20240716.00-0ubuntu1~16.04.0+esm3) @ xenial | 2026-06-29 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang.org/x/crypto | — | 0.52.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 9× in last 7d / 79× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 296 total refreshes for this CVE.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 20:38 UTCEG score recompute
- 2026-06-29 20:38 UTCVendor advisory
- 2026-06-29 16:40 UTCEG score recompute
- 2026-06-29 16:40 UTCVendor advisory
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-28 11:53 UTCEG score recompute
- 2026-06-28 11:53 UTCVendor advisory
- 2026-06-28 07:50 UTCEG score recompute
- 2026-06-28 07:50 UTCVendor advisory
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 03:28 UTCEG score recompute
- 2026-06-28 03:28 UTCVendor advisory
- 2026-06-27 23:30 UTCEG score recompute
- 2026-06-27 23:30 UTCVendor advisory
- 2026-06-27 19:32 UTCEG score recompute
- 2026-06-27 19:32 UTCVendor advisory
- 2026-06-27 11:51 UTCEG score recompute
- 2026-06-27 11:51 UTCVendor advisory
- 2026-06-27 07:21 UTCEG score recompute
- 2026-06-27 07:21 UTCVendor advisory
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 23:18 UTCEG score recompute
- 2026-06-26 23:18 UTCVendor advisory
- 2026-06-26 19:14 UTCEG score recompute
- 2026-06-26 19:14 UTCVendor advisory
- 2026-06-26 03:18 UTCEG score recompute
- 2026-06-26 03:18 UTCVendor advisory
- 2026-06-25 23:15 UTCEG score recompute
- 2026-06-25 23:15 UTCVendor advisory
- 2026-06-25 18:20 UTCEG score recompute
- 2026-06-25 18:20 UTCVendor advisory
- 2026-06-25 14:09 UTCEG score recompute
- 2026-06-25 14:09 UTCVendor advisory
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 03:52 UTCEG score recompute
- 2026-06-18 03:52 UTCVendor advisory
- 2026-06-17 23:54 UTCEG score recompute
- 2026-06-17 19:56 UTCEG score recompute
- 2026-06-17 19:56 UTCVendor advisory
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 14:55 UTCEG score recompute
- 2026-06-17 10:58 UTCEG score recompute
- 2026-06-17 03:24 UTCEG score recompute
- 2026-06-16 23:26 UTCEG score recompute
- 2026-06-16 23:26 UTCVendor advisory
- 2026-06-16 19:28 UTCEG score recompute
- 2026-06-16 19:28 UTCVendor advisory
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 10:42 UTCEG score recompute
- 2026-06-16 10:42 UTCVendor advisory
- 2026-06-16 06:42 UTCEG score recompute
- 2026-06-16 06:42 UTCVendor advisory
- 2026-06-16 02:45 UTCEG score recompute
- 2026-06-16 02:45 UTCVendor advisory
- 2026-06-15 22:45 UTCEG score recompute
- 2026-06-15 22:45 UTCVendor advisory
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 14:58 UTCEG score recompute
- 2026-06-15 14:58 UTCVendor advisory
- 2026-06-15 06:19 UTCEG score recompute
- 2026-06-15 06:19 UTCVendor advisory
- 2026-06-15 02:17 UTCEG score recompute
- 2026-06-15 02:17 UTCVendor advisory
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 22:18 UTCEG score recompute
- 2026-06-14 22:18 UTCVendor advisory
- 2026-06-14 18:21 UTCEG score recompute
- 2026-06-14 18:21 UTCVendor advisory
- 2026-06-14 14:04 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-39834?
When was CVE-2026-39834 disclosed?
Is CVE-2026-39834 actively exploited?
What is the CVSS score of CVE-2026-39834?
How do I remediate CVE-2026-39834?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39834
Is Your Infrastructure Affected by CVE-2026-39834?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.