CVE-2026-39834

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — Patch released this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated May 28, 2026
No patch confirmed yet.
generic

GO-2026-5020 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5020
generic
https://groups.google.com/g/golang-announce/c/a082jnz-LvI
generic

x/crypto/ssh: infinite loop on large channel writes · Issue #79567 · golang/go · GitHub

https://go.dev/issue/79567
generic
https://go.dev/cl/781663

Vendor Advisories for CVE-2026-39834(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulxd-tools (2.0.11-0ubuntu1~16.04.4+esm3) @ xenial2026-07-26ubuntu
ubuntugoogle-guest-agent (20250116.00-0ubuntu1~22.04.3) @ jammy2026-07-26ubuntu
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat

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)
PackageVulnerable rangeFixed inDependents
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 14× in last 7d / 49× 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 203 total refreshes for this CVE.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 08:08 UTCEG score recompute
  4. 2026-07-26 08:08 UTCVendor advisory
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:10 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 23:29 UTCOSV refresh
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 75 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 20:38 UTCVendor advisory
  15. 2026-06-29 16:40 UTCVendor advisory
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 11:53 UTCVendor advisory
  19. 2026-06-28 07:50 UTCVendor advisory
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 03:28 UTCVendor advisory
  22. 2026-06-27 23:30 UTCVendor advisory
  23. 2026-06-27 19:32 UTCVendor advisory
  24. 2026-06-27 11:51 UTCVendor advisory
  25. 2026-06-27 07:21 UTCVendor advisory
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-26 23:18 UTCVendor advisory
  28. 2026-06-26 19:14 UTCVendor advisory
  29. 2026-06-26 03:18 UTCVendor advisory
  30. 2026-06-25 23:15 UTCVendor advisory
  31. 2026-06-25 18:20 UTCVendor advisory
  32. 2026-06-25 14:09 UTCVendor advisory
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-25 13:49 UTCEPSS rescore
  35. 2026-06-24 14:05 UTCEPSS rescore
  36. 2026-06-23 21:33 UTCEPSS rescore
  37. 2026-06-22 14:25 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-21 14:56 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 01:59 UTCEPSS rescore
  42. 2026-06-19 19:25 UTCEPSS rescore
  43. 2026-06-18 17:52 UTCEPSS rescore
  44. 2026-06-18 17:52 UTCEPSS rescore
  45. 2026-06-18 03:52 UTCVendor advisory
  46. 2026-06-17 19:56 UTCVendor advisory
  47. 2026-06-17 17:53 UTCEPSS rescore
  48. 2026-06-16 23:26 UTCVendor advisory
  49. 2026-06-16 19:28 UTCVendor advisory
  50. 2026-06-16 17:52 UTCEPSS rescore
  51. 2026-06-16 10:42 UTCVendor advisory
  52. 2026-06-16 06:42 UTCVendor advisory
  53. 2026-06-16 02:45 UTCVendor advisory
  54. 2026-06-15 22:45 UTCVendor advisory
  55. 2026-06-15 17:49 UTCEPSS rescore
  56. 2026-06-15 14:58 UTCVendor advisory
  57. 2026-06-15 06:19 UTCVendor advisory
  58. 2026-06-15 02:17 UTCVendor advisory
  59. 2026-06-14 23:18 UTCEPSS rescore
  60. 2026-06-14 22:18 UTCVendor advisory
  61. 2026-06-14 18:21 UTCVendor advisory
  62. 2026-06-14 14:04 UTCVendor advisory
  63. 2026-06-14 10:01 UTCVendor advisory
  64. 2026-06-14 06:01 UTCVendor advisory
  65. 2026-06-14 01:52 UTCVendor advisory
  66. 2026-06-13 23:00 UTCEPSS rescore
  67. 2026-06-13 10:38 UTCVendor advisory
  68. 2026-06-13 06:26 UTCVendor advisory
  69. 2026-06-13 02:28 UTCVendor advisory
  70. 2026-06-12 23:12 UTCEPSS rescore
  71. 2026-06-12 23:12 UTCEPSS rescore
  72. 2026-06-12 22:30 UTCVendor advisory
  73. 2026-06-12 18:33 UTCVendor advisory
  74. 2026-06-12 14:35 UTCVendor advisory
  75. 2026-06-12 10:34 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-39834?
CVE-2026-39834 is a critical vulnerability published on May 22, 2026. 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.
When was CVE-2026-39834 disclosed?
CVE-2026-39834 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39834 actively exploited?
CVE-2026-39834 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.6% of all scored CVEs.
What is the CVSS score of CVE-2026-39834?
CVE-2026-39834 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-39834?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39834, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39834

Explore →

Is Your Infrastructure Affected by CVE-2026-39834?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs