EUVD-2026-20014Published

Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls

Explicit identifiers and source references

These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.

CVE-2026-32283 · Microsoft / collected KEV context

EUVD-2026-20014

GHSA-jrg3-gfjw-hm96

GO-2026-4870

BIT-golang-2026-32283

cve-program · CVE-2026-32283

euvd · EUVD-2026-20014

nvd · CVE-2026-32283

osv · GO-2026-4870

Related operational evidence

Explicit CVE identifiers

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 … · Advisory content revised · 9 Nov 2026
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 … · Advisory content revised · 7 Nov 2026
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 … · Advisory content revised · 1 Nov 2026
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 … · Advisory content revised · 30 Oct 2026
Release 2026-05-29 · Tool release · 4 Jun 2026