OpenSSL patches a DTLS flaw that sends heap memory to unauthenticated peers
OpenSSL patched 14 flaws, led by CVE-2026-84782, a CVSS 8.2 DTLS handshake bug that lets an unauthenticated remote peer pull fragments of heap memory. Only software that speaks DTLS is exposed, so VPN, VoIP and IoT products go first in the patch queue.
The Watch · Security desk
What happened
- The bug fires when OpenSSL retransmits a handshake message while sending another is stalled, and leftover heap data then goes to the other party in plaintext.
- If that read runs into unmapped memory, the application crashes instead, leaving a denial-of-service condition.
- A second OpenSSL flaw, the medium-severity CVE-2026-84783, lets a remote unauthenticated peer crash a multi-threaded TLS client.
- WolfSSL shipped version 5.9.4 on September 25 with fixes for 11 vulnerabilities, three of them rated high severity.
Why it matters
- Who has to decide decision Patch order can follow protocol use. DTLS-speaking VPN, VoIP and IoT systems go ahead of TLS-only OpenSSL deployments, since only DTLS reaches the high-severity bug.
- Who's exposed exposure Any service answering DTLS handshakes from untrusted networks can have heap memory read or be crashed by a peer holding no credentials.
- Who has to decide decision Mixed stacks cannot be ranked on the OpenSSL score alone. A WolfSSL client that accepts a forged CA clone lets a malicious server pass as authentic, so those fixes belong in the same patch window.
According to SecurityWeek, the flaw can be exploited over the network with no authentication and no user interaction [4]. The harder requirement is timing, and how reliably a hostile peer can force it decides whether the bug works against every exposed endpoint. OpenSSL has to be retransmitting one handshake message while sending another is stalled [2].
The scope is narrow and easy to check. The flaw is in the DTLS handshake, so an OpenSSL application serving only TLS over TCP is outside CVE-2026-84782 [18]. DTLS is common in VPNs, VoIP and IoT products [1], and those go first.
Most of the 12 low-severity OpenSSL fixes [17] end in denial of service through memory or CPU exhaustion, process crashes, or terminated DTLS 1.2 connections [7]. The terminated-connection bugs hit the same DTLS deployments [7]. The rest let attackers abuse QUIC servers for DDoS amplification or use timing side channels that could lead to private key recovery [8].
WolfSSL's high-severity fixes deal with a different attacker: a malicious server that gets past peer authentication in certain configurations [10]. In CVE-2026-93302, WolfSSL ignores the public key when it matches a certificate against a trusted peer certificate [11]. A server that knows which CAs a client trusts can present a forged clone of one and bypass authentication [11]. Builds made for Nginx, HAProxy, Stunnel and Apache httpd are among those affected [12].
CVE-2026-89102 lets anyone holding a certificate and private key that chain to a trusted CA forge certificates for arbitrary identities [13]. CVE-2026-89136 hits clients with Raw Public Key support enabled. The malicious server selects an RPK certificate type the client never requested [14].
The four medium-severity WolfSSL bugs include a handshake sequencing error. Between them, they can let an attacker complete a TLS 1.2 or DTLS 1.2 handshake in place of the legitimate server [15]. Most of the four low-severity bugs need specific configurations or legacy API usage [16].
SecurityWeek's report does not list fixed OpenSSL version numbers or describe exploitation in the wild for any of the 25 fixes across both libraries [19].
What to watch
- Published detail from OpenSSL or researchers on how reliably a peer can force the stalled-send retransmission state behind CVE-2026-84782.
- Advisories and fixed firmware from VPN, VoIP and IoT vendors whose DTLS stacks are built on OpenSSL.
- Any report of CVE-2026-84782 or the WolfSSL authentication bypasses being exploited in the wild.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence74
- Adoption40
- Hype gap+25
- Incentives30
- Confidence70
Perspective Coverage
4 publishers- Builder
- Builder 40%
- Operator
- Operator 54%
- Investor
- Investor 6%
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
CVE-2026-84782 could allow a remote peer to obtain fragments of heap memory or crash applications that use Datagram TLS (DTLS), a protocol commonly found in VPNs, VoIP and IoT products.
- [2]
The flaw is triggered during the DTLS handshake when OpenSSL retransmits a message while sending another one is stalled, which can cause leftover heap data to be sent to the other party in plaintext.
- [3]
If the read reaches unmapped memory, the application crashes, resulting in a denial-of-service condition.
- [4]
CVE-2026-84782 has a CVSS score of 8.2 and can be exploited over the network without authentication or user interaction.
- [5]
OpenSSL fixed 14 vulnerabilities, one of which is rated high severity.
- [6]
The OpenSSL releases also fix medium-severity CVE-2026-84783, which a remote, unauthenticated peer could exploit to crash a multi-threaded TLS client.
- [7]
The remaining OpenSSL flaws are rated low severity and mostly lead to denial of service through excessive memory or CPU consumption, process crashes, or termination of DTLS 1.2 connections.
- [8]
The rest of the low-severity OpenSSL flaws could let attackers abuse QUIC servers for DDoS amplification or exploit timing side channels to gather information that could lead to private key recovery.
- [9]
WolfSSL released version 5.9.4 on September 25, patching 11 vulnerabilities, three of them high severity.
- [10]
The high-severity WolfSSL issues can allow attackers to bypass peer authentication in certain WolfSSL configurations.
- [11]
CVE-2026-93302 exists because WolfSSL ignores the public key when matching a certificate against a trusted peer certificate; a malicious server that knows which CAs a client trusts can present a forged CA clone and bypass authentication.
- [12]
Builds affected by CVE-2026-93302 include those created for integration with Nginx, HAProxy, Stunnel, Apache httpd and other applications.
- [13]
CVE-2026-89102 allows an attacker holding any certificate and its private key that chains to a CA trusted by the client to forge certificates for arbitrary identities.
- [14]
CVE-2026-89136 lets a malicious server bypass authentication on clients with Raw Public Key support enabled by selecting an RPK certificate type the client never requested.
- [15]
Four medium-severity WolfSSL flaws involve certificate validation defects and a handshake sequencing error, and could allow attackers to bypass name constraints, plant an unverified CA in the shared certificate manager, or complete a TLS 1.2 or DTLS 1.2 handshake in place of the legitimate server.
- [16]
The four low-severity WolfSSL bugs could lead to a use-after-free during connection shutdown, skipped CRL revocation checks, acceptance of certificates with invalid signatures, and server impersonation; most require specific configurations or legacy API usage.
- [17]
12 of the 14 OpenSSL fixes are rated low severity.
- [18]
CVE-2026-84782 is reached through the DTLS handshake, so OpenSSL applications that do not use DTLS, such as TLS-over-TCP-only services, are outside this flaw.
- [19]
The OpenSSL and WolfSSL releases together fix 25 vulnerabilities.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
3 independent publishers whose own reporting we read for this story.
- scworld.comHigh-severity OpenSSL flaw can leak memory or crash programs
1 article · September 30, 2026
- securityweek.comHigh-Severity Vulnerabilities Patched in OpenSSL, WolfSSL
1 article · September 29, 2026
- thecyberexpress.comOpenSSL Flaw Could Expose Heap Memory and Crash Applications
1 article · September 30, 2026
- thehackernews.comOpenSSL Fixes High-Severity DTLS Flaw That Can Leak Heap Memory Unencrypted
2 articles · September 30, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Cryptographic library securityFollow
- Datagram TLS (DTLS)Follow
- Software End-of-LifeFollow