OpenSSL Patches Critical DTLS Memory Leak and Crash Vulnerability
Heap memory exposure and denial-of-service risk in DTLS handshake resend logic
Key Takeaways
- OpenSSL patched a high-severity DTLS vulnerability disclosed on September 29, 2026.
- The flaw can cause heap memory leakage or crashes during handshake message resend scenarios.
- Affected versions include OpenSSL 3.2 and 3.1 series; users should upgrade to the fixed releases.
- Exploitation requires specific DTLS handshake timing conditions but could lead to unencrypted memory disclosure.
- No confirmed active exploitation in the wild, but the flaw is reproducible under the described conditions.
Quick answers
- What happened?
- OpenSSL has addressed a high-severity vulnerability in its DTLS implementation that could allow heap memory leakage or program crashes during handshake message resend scenarios. The flaw stems from improper timing handling when larger handshake messages are partially outstanding and a resend is triggered.
- Which products are affected?
- OpenSSL
- What should defenders do?
- Upgrade to OpenSSL 3.2.0 or later, or OpenSSL 3.1.3 or later, depending on the release series. Monitor OpenSSL security advisories for exact version mappings and apply patches promptly.
OpenSSL released security updates on September 29, 2026, to resolve a high-severity flaw in the Datagram Transport Layer Security (DTLS) implementation. DTLS, the UDP-based counterpart of TLS, is widely used to secure real-time communications, including VoIP, streaming, and gaming traffic.
According to the OpenSSL security advisory, the vulnerability occurs when the DTLS stack resends a handshake message because no reply arrived before the timer expired. If a larger handshake message is already stuck part-way through the protocol stack at the moment the resend is initiated, the implementation mishandles the memory state, potentially exposing heap contents to the peer or causing the process to crash.
The issue affects all OpenSSL versions that support DTLS. Successful exploitation could allow a remote attacker to read heap memory contents unencrypted across a DTLS connection, or trigger a denial-of-service condition. OpenSSL has patched the flaw in the 3.2 and 3.1 release series. Users are advised to upgrade to the fixed versions immediately.
The OpenSSL team emphasized that while the conditions for exploitation are specific to DTLS handshake timing, the impact is significant due to the potential for memory disclosure without encryption. No active exploitation in the wild has been confirmed at the time of disclosure, but the reproducibility of the trigger conditions raises the risk profile.
Security Details
The vulnerability arises from improper handling of handshake message resend timing in the DTLS implementation when a larger message is partially outstanding. This can lead to heap memory exposure or program crashes.
Affected products
OpenSSL
Mitigation
Upgrade to OpenSSL 3.2.0 or later, or OpenSSL 3.1.3 or later, depending on the release series. Monitor OpenSSL security advisories for exact version mappings and apply patches promptly.
Sources
The Hacker News
OpenSSL Fixes High-Severity DTLS Flaw That Can Leak Heap Memory Unencrypted
Sep 30, 2026 · 08:09
Original link
Related Security News
CISA Advises of Sensitive Information Exposure in Johnson Controls EasyIO Neo Series Controllers
The Cybersecurity and Infrastructure Security Agency (CISA) has issued an Industrial Control Systems advisory regarding CVE-2026-64892, a vulnerability in Johnson Controls EasyIO Neo Series EC and CW Controllers that could allow an attacker to gain access to sensitive information. The flaw stems from improper access controls in building automation controllers and impacts four specific firmware versions. Johnson Controls has released fixed firmware versions V3.3b64 (EC) and V3.3b26 (CW) to address the issue.