RUSTSEC-2026-0285: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
The report identifies rustls 0.23.43 as affected and rustls 0.23.45 or newer as patched. Start by locating the repository's Rust dependency manifests and checking how rustls is resolved, then update the affected dependency and run the project's existing test suite to verify the driver still builds and tests pass.
Written by the indexing model from the issue text.
Description
TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
| Details | |
|---|---|
| Package | rustls |
| Version | 0.23.43 |
| URL | https://github.com/rustls/rustls/security/advisories/GHSA-2mjx-qc3c-rqvc |
| Date | 2026-09-14 |
| Patched versions | >=0.23.45 |
| Unaffected versions | <0.23.13 |
Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level
when they followed a key-changing message in the same record. For example,
a plaintext EncryptedExtensions message packed into the same record as the
ServerHello was accepted.
RFC 8446 section 5.1 requires that handshake messages do not span key changes,
and that implementations terminate the connection with an "unexpected_message"
alert if they do.
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 is functionally the same bug as Go's
GO-2026-4340 (CVE-2025-61730).
See advisory page for additional details.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/stackable-odbc-trino
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in stackabletech/stackable-odbc-trino
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
nautechsystems/nautilus_trader#5095 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stellar/rs-soroban-env#1739 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug good first issue package: quic
Difficulty 2/5 1-3 hours Newbie friendliness 78/100