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.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 14 Aug 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-1003 CWE-1015 CWE-606 |
Thu, 13 Aug 2026 23: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 |
Thu, 13 Aug 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Limit handshake messages we are willing to accept post-handshake in crypto/tls | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2026-08-13T21:58:53.216Z
Reserved: 2026-06-23T15:10:49.353Z
Link: CVE-2026-56862
No data.
Status : Received
Published: 2026-08-13T22:17:22.550
Modified: 2026-08-13T22:17:22.550
Link: CVE-2026-56862
No data.
OpenCVE Enrichment
Updated: 2026-08-14T00:15:04Z