Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 7.5epss 0.6%
probabilidad de explotación
0.6%top 52% de las CVE
explotación observada
noninguna fuente lo reporta
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Productos afectados
Go standard library · crypto/tlsReferencias
https://go.dev/cl/763767https://go.dev/issue/78334https://groups.google.com/g/golang-announce/c/0uYbvbPZRWUhttps://pkg.go.dev/vuln/GO-2026-4870https://access.redhat.com/security/cve/CVE-2026-32283https://bugzilla.redhat.com/show_bug.cgi?id=2456338https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32283.jsonhttps://access.redhat.com/errata/RHSA-2026:24762https://access.redhat.com/errata/RHSA-2026:41019https://access.redhat.com/errata/RHSA-2026:16101https://access.redhat.com/errata/RHSA-2026:54191https://access.redhat.com/errata/RHSA-2026:24761