rustls
Affected
- introduced
0.23.44, fixed0.23.46(semver)
Fixed versions
0.23.46
Fix
- Fixed version
0.23.46cargo update -p rustls --precise 0.23.46
Advisory
Also known as: CVE-2026-123612, RUSTSEC-2026-0347
rustls: ECH rejection can expose buffered application data to authenticated outer server before ech_required alert
In rustls 0.23.44 and 0.23.45, application data that a client buffers before the handshake completes is sent to the server even when the server rejects Encrypted Client Hello (ECH).
When the server rejects ECH, the client completes the handshake with the outer ClientHello and authenticates the server against the ECH config's public_name. At the end of the handshake, start_traffic() encrypts and queues any plaintext buffered by ClientConnection::writer(). It does this *before* checking for EchStatus::Rejected and queueing the ech_required alert.
The application then receives Error::PeerIncompatible(ServerRejectedEncryptedClientHello), as expected. However, the client is still expected to call write_tls() to send the fatal alert, and that call also sends the encrypted application data. The server decrypts the data and only then receives the alert.
The ordering bug is older than 0.23.44. Before 0.23.44, the client checked the server certificate against the inner server name rather than public_name, so a correctly configured server failed certificate verification first and no data was sent. 0.23.44 fixed that check, which makes the ordinary rejection path reachable.
Impact
Plaintext meant for the inner server, the one named in the encrypted ClientHello, goes to the client-facing server identified by public_name. That server is properly authenticated, so this is not an attack by an unauthenticated party. However this violates RFC 9849, which says the following:
public_name, and the connection "MUST NOT" be reported as successful to the application. rustls does report failure correctly. The problem is only that data is sent before the alert.This affects only clients that meet all of these conditions:
EchMode::Enable. GREASE ECH is not affected.The usual client response to rejection is to retry with the server's retry configs. In that case, the data has already gone to the outer server.
Low Basis: The source's own band: LOW
0.23.44, fixed 0.23.46 (semver)0.23.46
0.23.46cargo update -p rustls --precise 0.23.460.24.0-dev.1, fixed 0.24.0-dev.2 (semver)0.24.0-dev.2
0.24.0-dev.2cargo update -p rustls --precise 0.24.0-dev.2Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0