CVE-2026-93304

published 27 Sep 2026 · updated 1 Oct 2026

(D)TLS 1.2 client accepts early ChangeCipherSpec before ClientKeyExchange

6.3MediumCVSS 6.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

A (D)TLS 1.2 client can accept a ChangeCipherSpec message before it has sent its ClientKeyExchange. No master secret has been derived at that point, so the client installs read keys derived from a known (deterministic) key and checks the server's Finished against that same key. An out-of-order ChangeCipherSpec can therefore be used by an attacker to complete the handshake in place of the server and send data the client accepts as authentic. The client's own traffic still uses correctly derived keys, so the attacker cannot read it, and the genuine server never completes the handshake. DTLS 1.2 clients are exposed because a datagram read can deliver the out-of-order records on its own. TLS 1.2 clients are exposed when the application supplies received bytes with wolfSSL_inject() or enables read ahead. For certificate suites, the attacker must be in a man-in-the-middle position. For PSK (Pre Shared Key) connections, any fake server can succeed without knowing the PSK.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
wolfSSL>=4.7.0 <=5.9.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-93304 severity on Zeptric[![CVE-2026-93304](https://zeptric.io/badge/cve/CVE-2026-93304.svg)](https://zeptric.io/cve/CVE-2026-93304)