Skip to main content
CVE-2026-123613VulnerabilityPublished

Rustls from 0.23.13 before 0.23.45 accepts TLS 1.3 handshake messages at the wrong encryption level when they follow a

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123613· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.23.45 when convenient.

Data as of 8 Nov 2026, 06:21 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 0.23.45
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 7 Nov 2026.

What to do

Upgrade rustls to 0.23.45.

Affected software

ProductAffectedFixed in
rustlsrustlsAffected
  • >=0.23.13 <0.23.45
Fixed in
  • 0.23.45
crates.iorustlspkg:cargo/rustlsOther threatsAffected
  • >=0.23.13 <0.23.45
Fixed in
  • 0.23.45

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Rustls version 0.23.45 and later. Users should upgrade to version 0.23.45 or newer to remediate this vulnerability. No other mitigation steps are indicated.

Description

Rustls versions from 0.23.13 up to but not including 0.23.45 improperly accept TLS 1.3 handshake messages at incorrect encryption levels when these messages follow a key-changing message within the same record. This occurs because the Deframer::aligned function does not enforce the record-boundary alignment required by RFC 8446. An attacker, either a peer or someone on the communication path, can exploit this by packing a plaintext EncryptedExtensions message with the ServerHello, which rustls then accepts as unencrypted.

References

Community reviews

Loading reviews…