GHSA-2mjx-qc3c-rqvc: Rustls: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level when they followed a key-changing message in the same record. The handshake transcript is still authenticated, so a network-position attacker cannot use this to alter or complete a handshake; the practical effect is that a peer could send handshake messages that should be encrypted in plaintext without rustls rejecting the connection.
Published Oct 5, 2026 · Updated Oct 27, 2026
Affected packages
rustls
- Ecosystem
- Rust (crates.io)
- Affected
- >= 0.23.13, < 0.23.45
- Fixed in
- 0.23.45
- Check
cargo tree -i rustls
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level when they followed a key-changing message in the same record. The handshake transcript is still authenticated, so a network-position attacker cannot use this to alter or complete a handshake; the practical effect is that a peer could send handshake messages that should be encrypted in plaintext without rustls rejecting the connection.
This issue affects rustls versions 0.23.13 through 0.23.44 inclusive.
Original report
Summary
Rustls (tested version 0.23.44, and it appears still an issue on latest master though I have not tested this) accepts a TLS 1.3 server flight where a plaintext EncryptedExtensions is packed into the same record as the ServerHello.
This is very similar to Go's CVE-2025-61730 fixed in https://github.com/golang/go/commit/5046bdf8a612b35a2c1a9e168054c1d5c65e7dd7
Details
It appears Deframer::aligned considers itself aligned as long as all messages remaining in the buffer are complete. Rustls processes the ServerHello, installs the handshake keys, then pulls the complete (plaintext) EncryptedExtensions out of the buffer.
This is insufficient per RFC 8446 section 5.1's
Handshake messages MUST NOT span key changes. Implementations MUST verify that all messages immediately preceding a key change align with a record boundary; if not, then they MUST terminate the connection with an "unexpected_message" alert. Because the ClientHello, EndOfEarlyData, ServerHello, Finished, and KeyUpdate messages can immediately precede a key change, implementations MUST send these messages in alignment with a record boundary.
Impact
An on path attacker can inject plaintext messages that are accepted.
Tool Use Disclosure
This was discovered by a new TLS/DTLS test suite currently under construction. The specific testcase was inspired by the Go CVE. Other tested implementations (Botan, OpenSSL, BoringSSL, Go, wolfSSL) reject this protocol flow. Daybreak Blue reviewed the rustls code to identify probable root cause.
Credited to randombit, ranjiGT.
References
- https://github.com/rustls/rustls/security/advisories/GHSA-2mjx-qc3c-rqvc
- https://github.com/golang/go/commit/5046bdf8a612b35a2c1a9e168054c1d5c65e7dd7
- https://github.com/rustls/rustls/commit/98456aea708a7e3c6151e00ca2d4428e7a58257a
- https://rustsec.org/advisories/RUSTSEC-2026-0285.html
- https://github.com/rustls/rustls/pull/3265
- https://github.com/rustls/rustls/releases/tag/v/0.23.45
- https://github.com/advisories/GHSA-2mjx-qc3c-rqvc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Rust (crates.io) vulnerabilities
All Rust (crates.io) entriesGHSA-c8m5-c952-6cm4
Rustls: Session Debug formatting exposes TLS master secrets and resumption PSKs
medium4.0Oct 27, 2026GHSA-h2v8-394m-p7vv
Rustls: Brotli certificate decompression can allocate an attacker-controlled amount of memory up to 1 GiB before authentication.
low3.7Oct 27, 2026GHSA-vp88-798v-h67f
rustls: ECH rejection can expose buffered application data to authenticated outer server before `ech_required` alert
low2.3Oct 27, 2026GHSA-w44r-93j7-qv28
rustls: An unauthenticated ServerHello poisons the per-name key-exchange record, so later ClientHellos carry only a classical X25519 share
low3.7Oct 27, 2026GHSA-qg5g-gv98-5ffh
rustls network-reachable panic in `Acceptor::accept`
medium6.9Nov 25, 2024CVE-2024-32650
Denial of Service Vulnerability in Rustls Library
high7.5No fixApr 19, 2024
