cause OpenSSL to allocate a full message-length reassembly buffer for each
buffered message, so a small amount of wire data consumes a large amount of
memory.
Impact summary: A remote attacker can send a few small crafted DTLS handshake
fragments to make a DTLS server or client allocate well over a megabyte of
memory per connection, which may lead to memory exhaustion and Denial of
Service if many connections are made.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: DTLS handshake messages can arrive out of order and fragmented,
so OpenSSL buffers fragments of up to ten out-of-sequence messages until
reassembly is possible. When the first fragment of a new message arrives,
OpenSSL allocates a buffer sized to the full message length declared in the
fragment header, plus a reassembly bitmap, instead of storing only the bytes
actually received. The declared length is capped by the maximum certificate
list size, 128KB by default, and that cap applies to every handshake message
type rather than only to Certificate messages.
Only DTLS endpoints reach this code. TLS, QUIC and applications that do not
use DTLS are unaffected. An attacker sends fragments that declare a large
message length but carry almost no data, using up to ten distinct message
sequence numbers.
A single connection can then hold roughly 1.4MB of buffers from about 156
bytes on the wire. Because the number of buffered messages is capped, memory
exhaustion requires many connections or many peers, which is why the severity
is Low.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Nov 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. | Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages. Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers. A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low. FIPS impact: no The affected code is outside the FIPS module boundary. |
| Title | Remote DTLS Handshake Memory Exhaustion in OpenSSL | Excessive Memory Allocation in DTLS Handshake Message Reassembly |
| Weaknesses | CWE-770 |
Thu, 19 Nov 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Remote DTLS Handshake Memory Exhaustion in OpenSSL |
Thu, 19 Nov 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 18 Nov 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-400 |
Wed, 18 Nov 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openssl
Openssl openssl |
|
| Vendors & Products |
Openssl
Openssl openssl |
Wed, 18 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 18 Nov 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. | |
| References |
|
Status: PUBLISHED
Assigner: openssl
Published:
Updated: 2026-11-20T11:19:59.821Z
Reserved: 2026-09-22T14:18:48.634Z
Link: CVE-2026-95690
Updated: 2026-11-18T13:50:19.287Z
Status : Awaiting Analysis
Published: 2026-11-18T12:17:24.037
Modified: 2026-11-20T12:18:25.127
Link: CVE-2026-95690
No data.
OpenCVE Enrichment
Updated: 2026-11-19T09:45:22Z