CVE-2026-2645
Logic Flaw in wolfSSL TLS 1.2 Server State Machine
Publication date: 2026-03-19
Last updated on: 2026-04-29
Assigner: wolfSSL Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wolfssl | wolfssl | to 5.8.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-358 | The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in wolfSSL versions 5.8.2 and earlier, where a logic flaw in the TLS 1.2 server state machine allows the server to incorrectly accept the CertificateVerify message before receiving the ClientKeyExchange message. This breaks the expected sequence of the TLS handshake, potentially allowing protocol misuse or attacks that exploit this message order flaw.
How can this vulnerability impact me? :
The impact of this vulnerability is that an attacker could exploit the incorrect message ordering in the TLS handshake to potentially bypass certain security checks or cause unexpected behavior in the TLS server. This could lead to weakened security guarantees during the TLS handshake, possibly exposing communications to interception or manipulation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade wolfSSL to version 5.8.4 or later. Version 5.8.4 includes enhanced sanity checks on the ordering of TLS handshake messages for TLS 1.2 and earlier, preventing the server from incorrectly accepting the CertificateVerify message before the ClientKeyExchange message.
Additionally, version 5.9.0 further hardens the handshake process to catch this issue even earlier.