CVE-2026-32283

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-08. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
46.1%
KEV
Not listed

Published

April 8, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

GO-2026-4870 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4870
generic

crypto/tls: multiple key update handshake messages can cause connection to deadlock · Issue #78334 · golang/go · GitHub

https://go.dev/issue/78334

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatreceptor-0:1.6.5-1.el9ap2026-06-09redhat
redhatpodman-7:5.8.2-3.el10_22026-06-08redhat
redhatrhc-1:0.2.7-1.el9_6.42026-06-08redhat
redhatdelve-0:1.26.1-2.el10_22026-06-04redhat
redhatmulticluster-globalhub/multicluster-globalhub-agent-rhel9:17803208092026-06-04redhat
redhatimage-builder-0:52.1-1.el9_82026-06-04redhat
redhatdelve-0:1.25.2-4.el10_02026-06-04redhat
redhatosbuild-composer-0:165.1-2.el9_82026-06-03redhat
redhatrhc-1:0.3.2-4.el10_02026-06-03redhat
redhatimage-builder-0:52.1-1.el10_22026-06-03redhat
redhatosbuild-composer-0:132.2-7.el9_62026-06-03redhat
redhatmulticluster-globalhub/multicluster-globalhub-agent-rhel9:17792106752026-06-02redhat
redhatosbuild-composer-0:165.1-2.el10_22026-06-02redhat
redhatrh-lightspeed-runtimes/runtimes-inventory-rhel9-operator:1.0.3-17799961972026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-agent-rhel9:17798388192026-06-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-agent-rhel9:17798286912026-05-28redhat
redhatskopeo-2:1.18.1-5.el9_6.12026-05-26redhat
redhatbuildah-2:1.39.9-1.el9_62026-05-26redhat
redhatcontainernetworking-plugins-1:1.6.2-3.el9_6.12026-05-26redhat
redhatgrafana-0:10.2.6-21.el9_62026-05-26redhat
redhatpodman-6:5.4.0-15.el10_0.22026-05-26redhat
redhatskopeo-2:1.18.1-3.el10_0.22026-05-26redhat
redhatbuildah-2:1.39.9-1.el10_02026-05-26redhat
redhatgrafana-pcp-0:5.1.1-14.el9_62026-05-21redhat
redhatcontainer-tools:rhel8-8060020260515174849.ad008a3a2026-05-20redhat
redhatopentelemetry-collector-0:0.144.0-2.el9_42026-05-20redhat
redhatgit-lfs-0:3.6.1-2.el10_0.42026-05-20redhat
redhatgit-lfs-0:3.6.1-2.el9_6.42026-05-20redhat
redhatrhc-worker-playbook-0:0.2.3-5.el10_02026-05-20redhat

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
stdlib1.26.2

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 14× in last 7d / 46× 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 122 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-32283?
CVE-2026-32283 is a high vulnerability published on April 8, 2026. If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.
When was CVE-2026-32283 disclosed?
CVE-2026-32283 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32283 actively exploited?
CVE-2026-32283 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32283?
CVE-2026-32283 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32283?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32283, 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-32283

Explore →

Is Your Infrastructure Affected by CVE-2026-32283?

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