BIT-golang-2026-56862Published
Limit handshake messages we are willing to accept post-handshake 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-56862 · Microsoft / collected KEV context
cve-program · CVE-2026-56862
- https://go.dev/issue/80528
- https://go.dev/cl/804261
- https://groups.google.com/g/golang-announce/c/94pEornpRlI
- https://pkg.go.dev/vuln/GO-2026-6090
euvd · EUVD-2026-58511
- https://go.dev/issue/80528
- https://go.dev/cl/804261
- https://groups.google.com/g/golang-announce/c/94pEornpRlI
- https://pkg.go.dev/vuln/GO-2026-6090
nvd · CVE-2026-56862
- https://go.dev/cl/804261
- https://go.dev/issue/80528
- https://groups.google.com/g/golang-announce/c/94pEornpRlI
- https://pkg.go.dev/vuln/GO-2026-6090
osv · GO-2026-6090
Related operational evidence
Explicit CVE identifiers- 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 pe… · Advisory content revised · 7 Nov 2026
- 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 pe… · Advisory content revised · 5 Nov 2026
- 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 pe… · Advisory content revised · 1 Nov 2026