← Back to CVE intelligence
CVE intelligence

CVE-2026-95690

Vulnerability intelligence

Published Nov 18, 2026Sources checked Nov 21, 2026
5.3MEDIUMCVSS out of 10
What this means

Review the available evidence

CVE-2026-95690 and is rated Medium severity with a CVSS score of 5.3. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Microsoft Security Response Center guidance

Vendor revision: Nov 21, 2026

Release Notes

CISA KEVNot listedBased on the latest collected catalog
EPSS0.4%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-95690?

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.

Source: NVD