CVE-2026-123611: Rustls · Unauthenticated ServerHello can downgrade later connections to classical key exchange
Affects rustlsSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.23.46 when convenient.
Data as of 9 Nov 2026, 11:23 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.7 |
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.23.46
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade rustls to 0.23.46.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iorustlspkg:cargo/rustlsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fixed version of Rustls is available starting from version 0.23.46. Users should upgrade to Rustls 0.23.46 or later to remediate this issue. Additionally, servers that send HelloRetryRequests for their preferred key exchange groups are not affected. Clients with session resumption disabled are also not vulnerable. No other specific mitigation actions are required.
Description
Rustls versions before 0.23.46 have a vulnerability where an unauthenticated ServerHello message can cause the client to downgrade future TLS connections to classical key exchange only, losing post-quantum confidentiality. This occurs because the client records the server-selected key exchange group before server authentication and uses it for future connections. A network attacker can exploit this by responding with a ServerHello selecting a classical group, causing subsequent connections to omit the post-quantum hybrid key exchange. There is no key compromise or authentication bypass. The issue is fixed in Rustls 0.23.46.