Repository navigation
crypto/tls: multiple key update handshake messages can cause connection to deadlock #78334
Description
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.
Thank you to Jakub Ciolek - https://ciolek.dev/ for reporting this issue.
This is CVE-2026-32283 and Go issue https://go.dev/issue/78334.
This is a PRIVATE issue for CVE-2026-32283, tracked in http://b/489152979 and fixed by https://go-internal-review.git.corp.google.com/c/go/+/3881.
/cc @golang/security and @golang/release
Activity
neild commentedon Mar 27, 2026
@gopherbot please open backport issues for this security fix
gopherbot commentedon Mar 27, 2026
Backport issue(s) opened: #78427 (for 1.25), #78428 (for 1.26).
Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.
gopherbot commentedon Apr 7, 2026
Change https://go.dev/cl/763548 mentions this issue:
[release-branch.go1.26] crypto/tls: prevent deadlock when client sends multiple key update messagesgopherbot commentedon Apr 7, 2026
Change https://go.dev/cl/763555 mentions this issue:
[release-branch.go1.25] crypto/tls: prevent deadlock when client sends multiple key update messages[release-branch.go1.25] crypto/tls: prevent deadlock when client send…
[release-branch.go1.26] crypto/tls: prevent deadlock when client send…
[-]security: fix CVE-2026-32283[/-][+]crypto/tls: multiple key update handshake messages can cause connection to deadlock[/+]gopherbot commentedon Apr 7, 2026
Change https://go.dev/cl/763767 mentions this issue:
crypto/tls: prevent deadlock when client sends multiple key update messagescrypto/tls: prevent deadlock when client sends multiple key update me…
[release-branch.go1.26] crypto/tls: prevent deadlock when client send…
[release-branch.go1.26] crypto/tls: prevent deadlock when client send…