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.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 08 Apr 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go Standard Library
Go Standard Library crypto Tls |
|
| Vendors & Products |
Go Standard Library
Go Standard Library crypto Tls |
Wed, 08 Apr 2026 01:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2026-04-08T01:06:57.670Z
Reserved: 2026-03-11T16:38:46.556Z
Link: CVE-2026-32283
No data.
Status : Awaiting Analysis
Published: 2026-04-08T02:16:03.580
Modified: 2026-04-08T21:26:35.910
Link: CVE-2026-32283
No data.
OpenCVE Enrichment
Updated: 2026-04-08T19:44:18Z
Weaknesses
No weakness.