Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitypost-quantum-cryptography

Rustls 0.23.46 Fixes TLS Secret Exposure, Memory Exhaustion and Key-Exchange Downgrade

Vulnerability Disclosure · 5 sources · Updated 1mo ago · First seen Oct 14, 2026

Rustls 0.23.46 Fixes TLS Secret Exposure, Memory Exhaustion and Key-Exchange Downgrade

Rustls released version 0.23.46 to fix four security vulnerabilities affecting the Rust-based TLS library. A medium-severity flaw, RUSTSEC-2026-0346 (CVSS 4.0), exposes TLS 1.2 master secrets or TLS 1.3 resumption keys when applications log client session values using their debug formatting; ordinary connection and built-in session-cache debug output remain unaffected. A low-severity denial-of-service flaw, RUSTSEC-2026-0348, lets an unauthenticated peer trigger an allocation of up to 1 GiB with a five-byte Brotli header, potentially terminating the process. It affects deployments enabling the non-default Brotli feature: clients connecting to malicious servers and servers requesting client certificates. OpenAI discovered and reported 13 bugs fixed in the release, including two security issues.

The release also fixes two low-severity confidentiality weaknesses. RUSTSEC-2026-0349 allows an unauthenticated ServerHello to poison cached key-share predictions, potentially causing later connections to use classical X25519 rather than hybrid post-quantum key exchange. Exploitation depends on client session storage and server policy; it does not bypass authentication or directly compromise keys. RUSTSEC-2026-0347 affects versions 0.23.44–0.23.45, allowing buffered application data to reach an authenticated client-facing server after it rejects Encrypted Client Hello (ECH), despite the application receiving a rejection error. An unauthenticated party cannot exploit that flaw. Organizations should upgrade affected dependencies to 0.23.46 or later, review custom session-store logging for exposed secrets, and identify deployments using Brotli decompression, hybrid key exchange or ECH.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Oct 14, 2026
  1. Reported Oct 14, 20261mo ago

    OpenAI discovers and reports 13 bugs fixed in rustls 0.23.46

    OpenAI discovered and reported 13 bugs subsequently fixed in rustls 0.23.46, including two of the release's four security issues. The source does not identify which two security issues OpenAI reported.

    Rustls 0.23.46 Released With Four Security Fixes - Phoronix
  2. Oct 14, 20261mo ago

    RustSec discloses key-share prediction poisoning that can remove post-quantum protection

    RustSec issued RUSTSEC-2026-0349 for GHSA-w44r-93j7-qv28, a low-severity flaw allowing an unauthenticated ServerHello to poison cached key-share predictions and cause later connections to use classical-only X25519 when the genuine server accepts it. The flaw does not bypass authentication or compromise keys, and version 0.23.46 and later are patched.

    RUSTSEC-2026-0349: rustls: Unauthenticated ServerHello can downgrade later connections to classical key exchange › RustSec Advisory Database
  3. Oct 14, 20261mo ago

    RustSec discloses unauthenticated Brotli allocation denial-of-service flaw

    RustSec issued RUSTSEC-2026-0348 for GHSA-h2v8-394m-p7vv, revealing that a five-byte Brotli header can trigger a 1 GiB allocation before authentication and potentially abort the process. The low-severity flaw affects applications enabling the non-default brotli feature; versions before 0.23.9 are unaffected, and version 0.23.46 and later are patched.

    RUSTSEC-2026-0348: rustls: Brotli certificate decompression can allocate up to 1 GiB before authentication › RustSec Advisory Database
  4. Oct 14, 20261mo ago

    RustSec discloses buffered application-data leakage after ECH rejection

    RustSec issued RUSTSEC-2026-0347 for GHSA-vp88-798v-h67f, explaining how rustls clients can transmit buffered application data to an authenticated client-facing server after it rejects ECH. The low-severity flaw affects versions 0.23.44 through 0.23.45 and is patched in version 0.23.46.

    RUSTSEC-2026-0347: rustls: Buffered application data sent to outer server after ECH rejection › RustSec Advisory Database
  5. Oct 14, 20261mo ago

    RustSec issues advisory for TLS secrets exposed through session debug output

    RustSec issued RUSTSEC-2026-0346 for GHSA-c8m5-c952-6cm4, a medium-severity vulnerability that exposes TLS master secrets or resumption PSKs when custom session stores log session values using Debug formatting. Versions before 0.21.0 are unaffected, and version 0.23.46 and later contain the fix.

    RUSTSEC-2026-0346: rustls: `Debug` impls for client session values expose TLS secrets › RustSec Advisory Database
  6. Oct 14, 20261mo ago

    Rustls releases version 0.23.46 with four security fixes

    Rustls released version 0.23.46, fixing excessive Brotli decompression allocation, TLS secret exposure through session debug formatting, key-exchange prediction poisoning, and buffered application-data disclosure after ECH rejection. The release also included other bug fixes.

    Rustls 0.23.46 Released With Four Security Fixes - Phoronix
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.