
PEACH
Un cadre d’isolation des locataires
CVE-2026-123612 is an information disclosure vulnerability in the rustls TLS library affecting versions 0.23.44 and 0.23.45. When a server rejects an Encrypted Client Hello (ECH), application data buffered by the client before the handshake completes is incorrectly transmitted to the client-facing (outer) server rather than being discarded. The vulnerability was published on November 8, 2026, with a patch available in version 0.23.46. It carries a CVSS v3.1 score of 2.3 (Low) and a CVSS v4.0 score of 4.6 (Medium) (GitHub Advisory, rustls Advisory).
The root cause is classified as CWE-696 (Incorrect Behavior Order): the start_traffic() function encrypts and queues plaintext buffered via ClientConnection::writer() before checking for EchStatus::Rejected and queuing the ech_required fatal alert. When the application subsequently calls write_tls() to send the alert, the encrypted application data is transmitted first; the server decrypts it and only then receives the alert. This ordering bug predates version 0.23.44, but was latent because prior versions incorrectly validated the server certificate against the inner server name rather than public_name, causing certificate verification to fail before any data could be sent. The fix in 0.23.44 for that certificate check inadvertently made the data-leakage path reachable (rustls Advisory, GitHub Advisory). Exploitation requires the client to use EchMode::Enable (GREASE ECH is unaffected), write application data before the handshake completes, and connect to a server that rejects the ECH config (e.g., due to a stale config).
The confidentiality impact is limited: plaintext intended for the inner (hidden) server is exposed to the authenticated outer server identified by public_name. Because the outer server is properly authenticated, this is not an attack by an unauthenticated third party, but it violates RFC 9849 §6.1.6, which mandates that the client abort with an ech_required alert before sending any application data. There is no integrity or availability impact. The practical risk is that sensitive application-layer data (e.g., HTTP requests, credentials) written before handshake completion may be read by the outer server operator, undermining the privacy guarantees that ECH is designed to provide (rustls Advisory).
There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the disclosure date (GitHub Advisory). The EPSS score is approximately 0.11% (1st percentile), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation is non-automatable and requires high privileges on the local system, significantly limiting the attacker pool (GitHub Advisory).
The primary remediation is to upgrade rustls to version 0.23.46 or later, which corrects the ordering of the ech_required alert relative to application data transmission (GitHub Advisory). As a short-term workaround, applications can avoid writing data to ClientConnection::writer() before the TLS handshake has fully completed, or disable EchMode::Enable if ECH is not strictly required. Organizations should audit their Cargo dependency trees for transitive dependencies on rustls 0.23.44 or 0.23.45 and update accordingly.
The vulnerability was disclosed by the rustls maintainer (ctz) via a GitHub Security Advisory (GHSA-vp88-798v-h67f) on October 14, 2026, and assigned CVE-2026-123612 on November 8, 2026 (rustls Advisory). The advisory was noted on infosec.exchange and tracked by threat intelligence platforms including Tenable (plugin 377659) and VulnCheck, though no significant broader media coverage or notable researcher commentary beyond the official advisory has been observed.
Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.
devel
rust-rustls
noble
rust-rustls
noble (esm-apps)
rust-rustls
resolute
rust-rustls
resolute (esm-apps)
rust-rustls
Source: Ce rapport a été généré à l’aide de l’IA
Évaluation gratuite des vulnérabilités
Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."