CVE-2026-56862GO-2026-6090BIT-GOLANG-2026-56862
Limit handshake messages we are willing to accept post-handshake in crypto/tls
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.25.13, 1.26.6, 1.27.0-rc.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- crypto/tls
fixed in 1.25.13; From 1.26.0-0 · fixed in 1.26.6; From 1.27.0-0 · fixed in 1.27.0-rc.3
- stdlibGo
fixed in 1.25.13; From 1.26.0-0 · fixed in 1.26.6; From 1.27.0-0 · fixed in 1.27.0-rc.3