CVE-2026-54874: Excessive Memory Use Buffering DTLS Records for a Future Epoch
Excessive Memory Use Buffering DTLS Records for a Future Epoch
Other sources
Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/opensslto a version that resolves this vulnerability.Fixed in 3.5.7-1~deb13u2Fixed in 3.6.4-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.3.7-6 - Upgrade
Upgrade
OpenSSL 1.0.2to a version that resolves this vulnerability.Fixed in OpenSSL 1.0.2zr - Upgrade
Upgrade
OpenSSL 1.1.1to a version that resolves this vulnerability.Fixed in OpenSSL 1.1.1zi - Upgrade
Upgrade
OpenSSL 3.0to a version that resolves this vulnerability.Fixed in OpenSSL 3.0.22 - Upgrade
Upgrade
OpenSSL 3.4to a version that resolves this vulnerability.Fixed in OpenSSL 3.4.7 - Upgrade
Upgrade
OpenSSL 3.5to a version that resolves this vulnerability.Fixed in OpenSSL 3.5.8 - Upgrade
Upgrade
OpenSSL 3.6to a version that resolves this vulnerability.Fixed in OpenSSL 3.6.4 - Upgrade
Upgrade
OpenSSL 4.0to a version that resolves this vulnerability.Fixed in OpenSSL 4.0.2 - Compensating control
For OpenSSL DTLS servers, bound exposure by limiting the number of concurrent associations/connections at the application level (since this bounds total exposure when buffering up to 100 early/future-epoch records per connection).