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 amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch ca

영향받는 제품

• openssl openssl

참고 자료

• https://github.com/openssl/openssl/commit/4808b5d64176451f3d93d87d0ac9c81a9b13fb23
• https://github.com/openssl/openssl/commit/7110cb2f75806d0bf809eb2f90790d477900be40
• https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
• https://github.com/openssl/openssl/commit/cc0c6710917cd5eec001b297355d2ba723505107
• https://github.com/openssl/openssl/commit/f52ffc11b90737ac89083909618dc2e1f42c561c
• https://openssl-library.org/news/secadv/20260825.txt