rustls handshake encryption bypass in TLS 1.3 record handling
rustls
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rustls crates.io |
|
|
Original description
Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a key-changing message in the same record, because Deframer::aligned does not enforce RFC 8446 record-boundary alignment. A peer or on-path attacker can pack a plaintext EncryptedExtensions with the ServerHello, which rustls accepts unencrypted.
From the CVE record · VulnCheck
References
- github.com/rustls/rustls/security/advisories/GHSA-2mjx-qc3c-rqvc
- github.com/rustls/rustls/commit/5046bdf8a612b35a2c1a9e168054c1d5c65e7dd7Patch
- vulncheck.com/advisories/rustls-0.23.13-before-0.23.45-tls-1.3-handshake-encryption-level-bypass
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/123xxx/CVE-2026-123613.json
- nvd.nist.gov/vuln/detail/CVE-2026-123613
- github.com/rustls/rustls/pull/3265
- github.com/golang/go/commit/5046bdf8a612b35a2c1a9e168054c1d5c65e7dd7
- github.com/rustls/rustls/commit/98456aea708a7e3c6151e00ca2d4428e7a58257a
- github.com/rustls/rustls
- github.com/rustls/rustls/releases/tag/v/0.23.45
- rustsec.org/advisories/RUSTSEC-2026-0285.html
- crates.io/crates/rustls