Advisory

RUSTSEC-2026-0285

Also known as: CVE-2026-123613, GHSA-2mjx-qc3c-rqvc

Summary

TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

Details

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).

Severity

Medium Basis: CVSS v3 score 5.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Dates

Published
2026-09-14 12:00 UTC
Modified
2026-11-09 09:21 UTC

Affected packages and fixes

rustls

crates.io · All systems

Affected

  • introduced 0.23.13, fixed 0.23.45 (semver)

Fixed versions

0.23.45

Fix

  • Fixed version 0.23.45
    cargo update -p rustls --precise 0.23.45

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences