CVE-2026-54874

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. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large...

CVE-2026-54874

CVE-2026-54874 is a memory amplification vulnerability in OpenSSL's DTLS implementation. When a handshake is in progress, OpenSSL buffers records belonging to a future epoch by retaining the full ~16 KB read buffer per record rather than only the actual record bytes. Up to 100 records per connect...

CVE-2026-54874

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. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large...

CVE-2026-54874

Excessive Memory Use Buffering DTLS Records for a Future Epoch...

OpenSSL 1.0.2 < 1.0.2zr Vulnerability

The version of OpenSSL installed on the remote host is prior to 1.0.2zr. It is, therefore, affected by a vulnerability as referenced in the 1.0.2zr advisory. - Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than...

OpenSSL: DTLS epoch record buffer memory DoS

The dtls1bufferrecord function in ssl/d1pkt.c in OpenSSL 0.9.8k and earlier 0.9.8 versions allows remote attackers to cause a denial of service memory consumption via a large series of "future epoch" DTLS records that are buffered in a queue, aka "DTLS record buffer limitation bug."...