CVE-2026-2646: 
wolfSSL vulnerability analysis and mitigation

CVE-2026-2646 is a heap-based buffer overflow vulnerability in wolfSSL's wolfSSL_d2i_SSL_SESSION() function, affecting all versions prior to 5.9.0. When the SESSION_CERTS compile-time option is enabled, certificate and session ID lengths are read from untrusted external input without bounds validation, allowing an attacker to overflow fixed-size heap buffers. The vulnerability was disclosed on March 19, 2026, and carries a CVSS v3.1 base score of 8.1 (High) (Feedly, GitHub PR #9748).

The root cause is classified as CWE-122 (Heap-based Buffer Overflow) and CWE-787 (Out-of-bounds Write). During deserialization of externally supplied SSL session data, the wolfSSL_d2i_SSL_SESSION() function reads length fields — including sessionIDSz, idLen, and sessionCtxSz — directly from the untrusted input blob without validating them against the fixed-size destination buffers (ID_LEN, SERVER_ID_LEN). This allows an attacker who can supply a maliciously crafted session blob to an application that loads external sessions to trigger heap memory corruption. Internally generated sessions are not affected, as the vulnerability requires externally sourced session data (GitHub PR #9748, GitHub PR #9949).

Successful exploitation can result in high confidentiality, integrity, and availability impact on the affected system, potentially enabling arbitrary code execution, sensitive data disclosure, or application crashes through heap corruption. The vulnerability affects applications using wolfSSL with SESSION_CERTS enabled that accept and deserialize session data from external or untrusted sources. Lateral movement is possible if the compromised process has elevated privileges or network access to other internal systems (Feedly).

1. Identify target: Locate an application using wolfSSL (versions < 5.9.0) compiled with SESSION_CERTS enabled that accepts and deserializes SSL session data from an external or untrusted source (e.g., a session cache loaded from disk or a network peer).
2. Craft malicious session blob: Construct a binary session blob where length fields such as sessionIDSz, idLen, or sessionCtxSz are set to values exceeding the fixed-size destination buffers (ID_LEN or SERVER_ID_LEN).
3. Deliver the payload: Supply the crafted session blob to the target application through whatever mechanism it uses to load external sessions (e.g., a session ticket, a shared session cache file, or a network protocol that passes session data).
4. Trigger deserialization: Cause the application to call wolfSSL_d2i_SSL_SESSION() on the malicious blob, triggering the missing bounds check and overflowing the fixed-size heap buffer.
5. Achieve heap corruption: Depending on heap layout and application context, leverage the overflow to achieve arbitrary code execution, crash the process, or corrupt adjacent heap objects for further exploitation (GitHub PR #9748, GitHub PR #9949).

• Logs: Application crash logs or core dumps referencing wolfSSL_d2i_SSL_SESSION or heap corruption errors in wolfSSL-linked processes.
• Process: Unexpected crashes or abnormal termination of TLS-enabled services using wolfSSL, particularly those that load session data from external sources.
• File System: Suspicious or malformed session cache files with oversized length fields in applications that persist SSL sessions to disk.
• Network: Anomalous TLS session resumption attempts with malformed session blobs sent to services using wolfSSL with SESSION_CERTS enabled.

Upgrade wolfSSL to version 5.9.0 or later, which includes the fixes from pull requests #9748 (merged February 10, 2026) and #9949 (merged March 12, 2026, targeting release 5.9.2). The patches add bounds checks for sessionIDSz, idLen, and sessionCtxSz against their respective fixed-size buffer limits before copying data. As a workaround, applications can disable the SESSION_CERTS compile-time option or avoid loading SSL session data from untrusted external sources until patching is feasible (GitHub PR #9748, GitHub PR #9949).