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.
Published:
2026-08-13
Score:
n/a
EPSS:
n/a
KEV:
No
Impact:
n/a
Action:
n/a
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
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 |
|
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-13T23:30:02Z
Weaknesses
No weakness.