OpenSSL · OpenSSL · published 2026-09-29

CVE-2026-84782DTLS Retransmits Handshake Messages From a Stale Buffer Offset

Routine No exploitation evidence; EPSS 0.9%.

CVE-2026-84782 is not known to be exploited in the wild. EPSS estimates a 0.9% chance of exploitation in the next 30 days, higher than 60% of all CVEs. This OpenSSL vulnerability: CVSS 8.2 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 4.0.3, 3.6.5, 3.5.9, 3.4.8 (+3 more); patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in OpenSSL 4.0.3, 3.6.5, 3.5.9, 3.4.8, 3.0.23, 1.1.1zj, 1.0.2zs.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixieopensslFixed in 3.5.7-1~deb13u3
12 bookwormopensslFixed in 3.0.22-1~deb12u2
Ubuntu (+4 more packages)26.04 LTSopensslFixed in 3.5.5-1ubuntu3.6
24.04 LTSopensslFixed in 3.0.13-0ubuntu3.16
22.04 LTSopensslFixed in 3.0.2-0ubuntu1.30
Red Hat Enterprise Linux (+63 more packages)RHEL 10opensslFixed in 3.5.8-2.el10_2 RHSA-2026:76918
RHEL 9opensslFixed in 3.5.8-2.el9_8 RHSA-2026:77396
RHEL 8opensslFixed in 1.1.1k-18.el8_6 RHSA-2026:85968

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Crypto libraryOpenSSL

    OpenSSL security fixes: 14 CVEs

    Upgrade to 4.0.33.6.53.5.93.4.83.0.231.1.1zj1.0.2zs

    Why: Vendor security release for server software (most severe: CVE-2026-84782).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.9% (61th pct)FIRST EPSS v2026.06.15
CVSS base score8.2 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →