OpenSSL Patches High-Severity Memory Leak Vulnerability

Key Takeaways

• OpenSSL has issued critical security updates to address a high-severity memory leak vulnerability.
• The flaw, identified as CVE-2026-84782, affects numerous OpenSSL versions and could expose sensitive heap memory during DTLS handshakes.
• The vulnerability can also trigger a denial-of-service condition by crashing affected processes.
• Patched versions include OpenSSL 4.0.3, 3.6.5, 3.5.9, and 3.4.8, with fixes for older branches available to premium support customers.

OpenSSL Patches High-Severity Memory Leak Vulnerability

OpenSSL has released urgent security updates to mitigate a high-severity vulnerability that could lead to the exposure of heap memory in plaintext during Datagram Transport Layer Security (DTLS) handshakes. This critical flaw, officially designated CVE-2026-84782, stems from an out-of-bounds read error within the DTLS handshake retransmission logic.

Beyond memory leakage, the vulnerability also carries the risk of crashing an affected process, thereby creating a denial-of-service (DoS) condition. The OpenSSL Project announced these security releases on September 29, 2026, alongside updates for OpenSSL 4.0.3, 3.6.5, 3.5.9, and 3.4.8. These updates are described as comprehensive security patches, with CVE-2026-84782 being the most critical issue addressed, rated as High severity.

Understanding the DTLS Handshake Flaw

DTLS extends the security features of Transport Layer Security (TLS) to unreliable datagram protocols, which are inherently susceptible to packet loss, reordering, or delays. To counteract these challenges, the DTLS handshake mechanism incorporates features like message fragmentation and the retransmission of previously sent data upon timer expiration.

The vulnerability, CVE-2026-84782, manifests when OpenSSL temporarily halts a handshake message write operation because the underlying transport mechanism cannot accept additional data, resulting in a WANT_WRITE return. While this write operation remains suspended, a retransmission timer can trigger a request to resend an earlier handshake message.

In vulnerable OpenSSL versions, the internal buffer and position tracking associated with the interrupted write are reused without properly resetting the read offset to the beginning of the message queued for retransmission. This oversight means the retransmission process can commence from an incorrect, stale position, potentially appending leftover bytes from a different, larger message and reading beyond the boundaries of the allocated buffer.

This erroneous behavior can lead to the transmission of adjacent heap memory contents to the connected peer as part of the plaintext handshake data. The specific bytes exposed are contingent on the surrounding process memory, meaning there is no fixed set of secret data that will invariably leak. Furthermore, if this out-of-bounds read attempts to access an unmapped memory region, the process may terminate abruptly, allowing an attacker to trigger a denial-of-service attack. OpenSSL categorizes this weakness under CWE-125: Out-of-bounds Read.

The bug also introduces a secondary state management issue. Even if a retransmission begins at the correct offset, completing it while another handshake write is paused can overwrite critical shared bookkeeping data needed to resume the original operation. Subsequent calls such as SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() might then encounter an inconsistent state relative to the suspended message, leading to an abort in debugging builds.

The Fix and Affected Versions

OpenSSL addressed CVE-2026-84782 by implementing two key changes: resetting the retransmission read position before any message resend, and preventing retransmission altogether while a handshake write is suspended, deferring this work until the original write operation resumes. The project confirms that the affected logic resides outside the OpenSSL FIPS module boundary, ensuring FIPS modules remain unaffected.

All major OpenSSL branches were susceptible to this vulnerability:

• OpenSSL 4.0 prior to 4.0.3
• OpenSSL 3.6 prior to 3.6.5
• OpenSSL 3.5 prior to 3.5.9
• OpenSSL 3.4 prior to 3.4.8
• OpenSSL 3.0 prior to 3.0.23
• OpenSSL 1.1.1 prior to 1.1.1zj
• OpenSSL 1.0.2 prior to 1.0.2zs

It’s important to note that fixes for the three oldest branches (3.0, 1.1.1, and 1.0.2) are exclusively available to premium support customers.

The vulnerability was reported by Laurent Gaffie of Secorizon on August 17, 2026, and Ryan Hooper developed the corrective patch after receiving the report in August.

Beyond CVE-2026-84782, OpenSSL 4.0.3 also resolves 13 other vulnerabilities impacting various components, including X.509 processing, QUIC, CMP, DTLS, SM2, and elliptic-curve operations. This comprehensive update underscores the importance of applying the latest releases.

What You Should Do

• Identify Affected Systems: System administrators must conduct a thorough inventory of all appliances, embedded systems, VPN products, and applications that utilize OpenSSL DTLS.
• Prioritize Upgrades: Immediately upgrade to the latest patched versions. For actively maintained branches, this means OpenSSL 4.0.3, 3.6.5, 3.5.9, or 3.4.8.
• Premium Support Customers: If you are on an older, supported branch (3.0, 1.1.1, or 1.0.2), obtain updates 3.0.23, 1.1.1zj, or 1.0.2zs through your premium support channel.
• Check All OpenSSL Instances: Be aware that many applications bundle their own OpenSSL libraries rather than relying on the system’s installed version. A simple check of the host package manager may not reveal all exposed copies. Ensure all bundled instances are also updated.
• Consult Vendors: For appliances and third-party products, follow upgrade instructions provided by your operating system or product vendor.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.