High severity · published Aug 13, 2026
CVE-2026-56862
Limit handshake messages we are willing to accept post-handshake in crypto/tls
7.5
CVSS
0.6%
EPSS
No
On KEV
Description
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indefinitely.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 47% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CR
crypto/tls · Go standard library
before 1.25.13; 1.26.0-0 before 1.26.6; 1.27.0-0 before 1.27.0-rc.3 · source: vendor
Affected product
CR
crypto/tls
Go standard library
More from crypto/tls
7.5
CVE-2026-97031
Reject malformed ECH outer extension references in crypto/tls
7.5
CVE-2026-32283
Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls
5.3
CVE-2026-42505
Invoking Encrypted Client Hello privacy leak in crypto/tls
3.1
CVE-2022-30629
Session tickets lack random ticket_age_add in crypto/tls