OpenSSL’s DTLS fix matters if you ship calls, WebRTC, or UDP TLS

By George Bailey   Published: 10/01/26   Updated: 10/14/26   4 min read

OpenSSL released fixes on September 29 for a high-severity DTLS flaw that can leak heap memory as unencrypted handshake data or crash the process. Only software that uses OpenSSL for DTLS (UDP TLS) is in scope, such as WebRTC data channels, VoIP keying and other UDP-secured paths.

Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.

Public fixes cover the 4.0, 3.6, 3.5, and 3.4 branches. OpenSSL 3.0’s public support ended September 7, so the 3.0.23 fix is premium-only unless your distro backported it. Ubuntu and Debian already shipped packages for several releases.

If your product speaks DTLS through OpenSSL, patch the handshake resend bug.

CVE-2026-84782: a resend timer that reuses the wrong buffer position

CVE-2026-84782 sits in DTLS handshake retransmission. DTLS fragments large handshake messages across UDP datagrams. If sending pauses mid-message and the resend timer fires, vulnerable OpenSSL used the paused buffer position instead of restarting the resent message. The peer could receive wrongly labeled handshake bytes that included leftover heap memory, or the process could crash on an overrun.

OpenSSL rates the issue High and advises installing High fixes as soon as possible. CISA scored it CVSS 8.2 with exploitation “none” at publication. Laurent Gaffie of Secorizon reported the bug; Ryan Hooper developed the fix. OpenSSL also shipped thirteen other fixes the same day; the next most serious (CVE-2026-84783, Moderate) affects only OpenSSL 4.0 multi-threaded certificate-chain builds.

DTLS users are exposed, and OpenSSL 3.0 has no public fix

Most TLS-over-TCP stacks are not exposed. Anything that terminates or initiates DTLS with a linked OpenSSL is, including WebRTC SFUs, some VPN concentrators, IoT stacks and custom UDP protocols. A memory leak plus a reliable crash path is reason enough to move the rebuild up the list, even without a public exploit.

OpenSSL 3.0 is the harder case. Teams still building or shipping 3.0 binaries have no public upstream fix. They must move to 3.5 LTS or 4.0, pay for a support contract, or rely on distro backports (Ubuntu 22.04/24.04 packages were updated September 29).

Find DTLS users, upgrade, and plan the 3.0 exit

Forward this

If you own a product or service that uses OpenSSL for DTLS (calls, WebRTC, UDP TLS): OpenSSL shipped a High fix for a handshake resend bug that can leak heap memory or crash the process. Please confirm you are on 4.0.3 / 3.6.5 / 3.5.9 / 3.4.8 or a distro package that includes CVE-2026-84782, and that anything still on OpenSSL 3.0 has a migration plan.

Details

Hunt / verify

OpenSSL CVE-2026-84782 (DTLS heap leak/crash) — upgrade to 4.0.3/3.6.5/3.5.9/3.4.8 or distro package; inventory DTLS/WebRTC users; plan exit from OpenSSL 3.0.

Sources

Stay Current

Newer CyberExperts coverage on this topic

This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.

Latest Daily Brief

Monday’s brief: Ivanti’s last VPN fix is due today, then WordPress update attacks, a fake Claude Code extension and Drupal stores

The fastest way to catch up on what changed after this article was published.

Read Today's Brief

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].