OpenSSL has published new security updates addressing a critical flaw that could cause the exposure of heap memory as plaintext during Datagram Transport Layer Security (DTLS) handshakes. This vulnerability, identified as CVE-2026-84782, originates from an out-of-bounds read within DTLS handshake retransmission logic, potentially leading to process crashes and denial-of-service attacks.
Understanding the Vulnerability
Revealed on September 29, 2026, by the OpenSSL Project, CVE-2026-84782 is part of a series of security updates released in versions 4.0.3, 3.6.5, 3.5.9, and 3.4.8. These updates are critical, with OpenSSL rating the most serious vulnerability in each release as High.
DTLS is designed to provide TLS-style encryption over unreliable datagram networks, which can suffer from delays, reordering, or packet loss. The vulnerability arises when OpenSSL suspends a handshake message transmission because the transport layer cannot handle additional data, resulting in a WANT_WRITE condition. If a retransmission timer triggers during this suspension, previous messages may be resent incorrectly, exposing adjacent heap memory as plaintext.
Technical Insights and Impact
The flaw occurs because the system mistakenly reuses buffer and position tracking from the paused transmission without resetting the read offset. This oversight allows the retransmission to begin at an incorrect position, potentially appending extraneous bytes from a larger message and reading beyond the intended buffer limits.
Such behavior risks leaking plaintext data to connected peers, with the specific bytes exposed depending on the surrounding memory contents. If the vulnerability affects an unmapped memory region, it can lead to process termination, allowing remote peers to instigate denial-of-service conditions. OpenSSL categorizes this flaw under CWE-125, indicating an out-of-bounds read issue.
Resolution and Recommendations
To mitigate this vulnerability, OpenSSL developers have updated the software to reset retransmission read positions before resending messages. Furthermore, retransmissions are now skipped while handshake writes remain suspended, postponing actions until a later resumption call. Notably, this issue lies outside the OpenSSL FIPS module boundary, so FIPS modules remain unaffected.
The vulnerability affects all OpenSSL branches: 4.0 before 4.0.3, 3.6 before 3.6.5, 3.5 before 3.5.9, 3.4 before 3.4.8, 3.0 before 3.0.23, 1.1.1 before 1.1.1zj, and 1.0.2 before 1.0.2zs. Patches for older branches are available only to premium support customers.
Administrators are urged to review systems using OpenSSL DTLS, including appliances, embedded systems, VPN products, and applications, and to update them through their respective vendors. For comprehensive protection, ensure that all bundled OpenSSL versions within applications are also updated.
The vulnerability was initially reported by Laurent Gaffie of Secorizon on August 17, 2026, with the fix developed by Ryan Hooper following the report. OpenSSL version 4.0.3 additionally addresses 13 other vulnerabilities affecting various cryptographic processes, emphasizing the importance of treating this release as a critical security update.
