Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-32283US | high7.5 | — | ||
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.… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:10217WEB
- https://access.redhat.com/errata/RHSA-2026:10219WEB
- https://access.redhat.com/errata/RHSA-2026:10704WEB
- https://access.redhat.com/errata/RHSA-2026:11507WEB
- https://access.redhat.com/errata/RHSA-2026:11514WEB
- https://access.redhat.com/errata/RHSA-2026:11704WEB
- https://access.redhat.com/errata/RHSA-2026:11711WEB
- https://access.redhat.com/errata/RHSA-2026:11712WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan