Description
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.
Published: 2026-09-27
Score: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Authentication Bypass
Action: Patch Immediately
AI Analysis

Impact

A TLS 1.2 or DTLS 1.2 client that implements the wolfSSL library can accept a ChangeCipherSpec message before it has sent its ClientKeyExchange. At that moment no master secret has been derived, so the client installs read keys derived from a deterministic key and validates the server’s Finished message against that same key. An attacker can therefore insert an out‑of‑order ChangeCipherSpec in the handshake and complete the handshake in place of the real server, causing the client to accept data that the attacker has sent as authentic. The client’s outgoing traffic still uses properly derived keys, so the client cannot read the attacker’s data and the genuine server never completes a handshake. In DTLS 1.2 clients the out‑of‑order packet can be delivered by normal datagram delivery, while in TLS 1.2 clients the attacker must supply the bytes via wolfSSL_inject() or enable read‑ahead. For certificate‑based suites a man‑in‑the‑middle position is necessary, whereas for PSK connections any fake server can succeed without knowing the PSK.

Affected Systems

The vulnerability affects the wolfSSL library, used by any application that implements TLS 1.2 or DTLS 1.2 clients built with this library. No specific version range is cited, so all current releases that allow early ChangeCipherSpec acceptance are potentially affected.

Risk and Exploitability

The vulnerability carries a CVSS score of 6.3, indicating a moderate severity. The EPSS score is not available, so the likelihood of exploitation is unknown, but the attack requires the attacker to be able to inject records – either by exploiting DTLS datagram reordering or by acting as a man‑in‑the‑middle in TLS. The vulnerability is not listed in the CISA KEV catalog. Because the attacker can impersonate the server and send data accepted by the client, there is a real risk of authentication bypass, but the client cannot read the attacker’s data, limiting potential damage. The risk is higher for deployments that use PSK connections or enable read‑ahead, and lower for strictly certificate‑based connections with no MITM.

Generated by OpenCVE AI on September 27, 2026 at 10:24 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest wolfSSL patch that enforces proper sequencing of ChangeCipherSpec
  • Disable read‑ahead or require injection via application only in trusted contexts
  • For DTLS clients, enforce strict ordering of inbound records or disable DTLS if not needed
  • Configure applications to use only certificate‑based suites when possible, as PSK connections are more vulnerable to the exploit.

Generated by OpenCVE AI on September 27, 2026 at 10:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 02 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Tue, 29 Sep 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sun, 27 Sep 2026 11:00:00 +0000

Type Values Removed Values Added
First Time appeared Wolfssl
Wolfssl wolfssl
Vendors & Products Wolfssl
Wolfssl wolfssl

Sun, 27 Sep 2026 09:30:00 +0000

Type Values Removed Values Added
Description 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.
Title (D)TLS 1.2 client accepts early ChangeCipherSpec before ClientKeyExchange
Weaknesses CWE-696
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: wolfSSL

Published:

Updated: 2026-09-29T16:43:16.572Z

Reserved: 2026-09-17T16:55:11.172Z

Link: CVE-2026-93304

cve-icon Vulnrichment

Updated: 2026-09-29T16:42:59.155Z

cve-icon NVD

Status : Analyzed

Published: 2026-09-27T10:16:59.563

Modified: 2026-10-02T18:41:59.093

Link: CVE-2026-93304

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-27T10:45:06Z

Weaknesses