CVE-2026-39830

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% 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: cisa-adp, epss
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.

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.

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
47%
KEV
Not listed

Published

May 22, 2026

Last Modified

August 28, 2026

Advisory Details (10)

Auto-updated Aug 29, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:36319
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:36207
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:36199
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:35833
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:29455
generic

GO-2026-5017 - Go Packages

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

x/crypto/ssh: client can cause server deadlock on unexpected responses · Issue #79564 · golang/go · GitHub

https://go.dev/issue/79564
generic
https://go.dev/cl/781664
generic
https://go.dev/cl/781640

Vendor Advisories for CVE-2026-39830(20)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-trainer-rhel9:17870890492026-08-27redhat
redhatopenshift4/ose-ovn-kubernetes-rhel9:17869553162026-08-25redhat
redhatoadp/oadp-velero-rhel9:17869445402026-08-25redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17866138052026-08-13redhat
redhatrhacm2/volsync-rhel9:17864566582026-08-12redhat
redhatopenshift-gitops-1/argocd-rhel9:17852113462026-08-10redhat
redhatopenshift-gitops-1/argocd-rhel8:17851492602026-08-10redhat
redhatoadp/oadp-velero-rhel9:17851808782026-08-06redhat
redhatconforma-cli-stack-v1-4-1.4.32026-08-05redhat
redhatcontainer-tools:rhel8-8080020260721142025.63b345852026-08-04redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-192026-07-29redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17847387582026-07-29redhat
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17845644382026-07-28redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17836121632026-07-16redhat
redhatrhtas/timestamp-authority-rhel9:17839686442026-07-16redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatrhtas/rekor-monitor-rhel9:17839685082026-07-16redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatrhtas/rekor-cli-rhel9:17839693652026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhem/flightctl-worker-rhel10:17841949712026-07-16redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.10.0-1 ... 1:0.53.0-1 (33 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.25.0-1 ... 1:0.53.0-1 (18 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto1:0.25.0-1 ... 1:0.52.0-1~bpo13+1 (16 versions)1:0.52.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto—0.52.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 22× in last 7d / 158× 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 372 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-39830?
CVE-2026-39830 is a critical vulnerability published on May 22, 2026. 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.
When was CVE-2026-39830 disclosed?
CVE-2026-39830 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39830 actively exploited?
CVE-2026-39830 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 52.9% of all scored CVEs.
What is the CVSS score of CVE-2026-39830?
CVE-2026-39830 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-39830?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39830, 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-39830

Explore →

Is Your Infrastructure Affected by CVE-2026-39830?

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

Start Free Scan →Browse All CVEs