Rustls TLS 1.3 Flaw Accepts Handshake Messages at Incorrect Encryption Levels
Vulnerability Disclosure · 2 sources · Updated 2mo ago · First seen Sep 14, 2026

Rustls has fixed a medium-severity TLS 1.3 protocol-handling flaw, tracked as RUSTSEC-2026-0285 and GHSA-2mjx-qc3c-rqvc, that accepted handshake messages crossing encryption-level boundaries if they followed a key-changing message in the same TLS record. This could allow, for example, an unencrypted EncryptedExtensions message to be accepted alongside ServerHello, contrary to RFC 8446 section 5.1.
The issue affects Rustls releases from 0.23.13 through versions before 0.23.45; versions earlier than 0.23.13 are unaffected. Rustls 0.23.45 remediates the defect. A network-position attacker cannot alter or complete the authenticated handshake because transcript authentication remains intact, but a peer could send handshake content in plaintext when it should have been encrypted without the connection being rejected. OpenSSL and BoringSSL are not affected; the flaw is functionally equivalent to Go advisory GO-2026-4340 / CVE-2025-61730.


