CVE-2026-32283
If one side of the TLS connection sends multiple key update …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- go.dev/cl/763767
- go.dev/issue/78334
- groups.google.com/g/golang-announce/c/0uYbvbPZRWU
- pkg.go.dev/vuln/GO-2026-4870
- access.redhat.com/errata/RHSA-2026:10217
- access.redhat.com/errata/RHSA-2026:10219
- access.redhat.com/errata/RHSA-2026:10704
- access.redhat.com/errata/RHSA-2026:11507
- nvd.nist.gov/vuln/detail/CVE-2026-32283
- cve.org/CVERecord?id=CVE-2026-32283
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.