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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

Published

April 8, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
Patch available.
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(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatosbuild-composer-0:75-10.el8_82026-09-17redhat
redhatgit-lfs-0:3.2.0-2.el9_2.102026-09-14redhat
redhattripleo-ansible-0:3.3.1-17.1.20260603190918.8debef3.el9ost2026-09-10redhat
redhatquay/quay-rhel8:17885943762026-09-10redhat
redhatquay/quay-rhel8:17885618412026-09-09redhat
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatquay/quay-rhel8:17885955742026-09-08redhat
redhatrhosdt/tempo-rhel9:17883564732026-09-08redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat
redhatrhoai/odh-trainer-rhel9:17870890492026-08-27redhat
redhatopenshift4/ose-ansible-rhel9-operator:17871052022026-08-26redhat
redhatcontainernetworking-plugins-1:1.4.0-7.rhaos4.15.el82026-08-26redhat
redhatopenshift4/ose-ansible-rhel9-operator:17870132512026-08-25redhat
redhatopenshift4/frr-rhel9:17870123762026-08-25redhat
redhatweb-terminal/web-terminal-exec-rhel9:17866548672026-08-18redhat
redhatweb-terminal/web-terminal-exec-rhel9:17866554672026-08-18redhat
redhatweb-terminal/web-terminal-exec-rhel9:17866546132026-08-18redhat
redhatweb-terminal/web-terminal-exec-rhel9:17866545962026-08-18redhat
redhatweb-terminal/web-terminal-exec-rhel9:17866556762026-08-18redhat
redhatetcd-0:3.3.23-22.el8ost2026-08-13redhat
redhatrhc-worker-script-0:0.11-1.el7_92026-08-12redhat
redhatgolang-github-danielqsj-kafka_exporter2026-08-12redhat
redhatcontainer-tools:rhel8-8060020260803064027.ad008a3a2026-08-06redhat
redhatcontainer-tools:rhel8-8080020260721142025.63b345852026-08-04redhat
redhatrhc-1:0.2.2-1.el9_2.32026-08-03redhat
redhatrhc-1:0.2.4-8.el9_42026-08-03redhat
redhatosbuild-composer-0:101.5-1.el8_102026-07-31redhat
redhatgrafana-pcp-0:5.1.1-5.el9_2.12026-07-29redhat
redhatgrafana-pcp-0:5.1.1-8.el9_42026-07-29redhat
redhatgolang-0:1.25.9-1.el9_22026-07-29redhat

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

(6 across 5 ecosystems)
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.251.25.0-1 ... 1.25.8-1 (9 versions)
  • every version up to 1.25.9-1: fixed in 1.25.9-1
—
golang-1.261.26.0-1, 1.26.1-1, 1.26~rc2-1, 1.26~rc3-1, 1.26~rc3-2
  • every version up to 1.26.2-1: fixed in 1.26.2-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
stdlib—
  • every version up to 1.25.9: fixed in 1.25.9
  • 1.26.0-0 up to 1.26.2: fixed in 1.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 8× in last 7d / 51× 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 377 total refreshes for this CVE.

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

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 on April 8, 2026, with the most recent update on September 18, 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 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-32283 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32283 are linked in the Vendor Advisories panel on this page.

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.