Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 16 Apr 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Golang
Golang go |
|
| CPEs | cpe:2.3:a:golang:go:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Golang
Golang go |
Tue, 14 Apr 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-770 |
Mon, 13 Apr 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
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 |
|
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2026-04-13T18:19:55.848Z
Reserved: 2026-03-11T16:38:46.556Z
Link: CVE-2026-32283
Updated: 2026-04-13T17:51:42.115Z
Status : Analyzed
Published: 2026-04-08T02:16:03.580
Modified: 2026-04-16T19:12:10.540
Link: CVE-2026-32283
No data.
OpenCVE Enrichment
Updated: 2026-04-14T16:40:15Z