Skip to content
Threat Brief

← All advisories

CVE-2026-95690

Medium 5.3No known exploitationFix available

Excessive Memory Allocation in DTLS Handshake Message Reassembly

Record last updated

CVSS score

5.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 29% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: CVE record (openssl))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
OpenSSLOpenSSLfrom 1.0.2 before 1.0.2zt1.0.2ztCVE Program
OpenSSLOpenSSLfrom 1.1.1 before 1.1.1zk1.1.1zkCVE Program
OpenSSLOpenSSLfrom 3.0.0 before 3.0.243.0.24CVE Program
OpenSSLOpenSSLfrom 3.5.0 before 3.5.103.5.10CVE Program
OpenSSLOpenSSLfrom 4.0.0 before 4.0.44.0.4CVE Program
OpenSSLOpenSSLfrom 4.1.0 before 4.1.14.1.1CVE Program

Timeline

  1. Disclosure

    CVE record published by openssl

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (openssl)

    Source: CVE record (openssl) (opens in a new tab)

Vendor guidance and references