In this article
Crafted DTLS fragments can make OpenSSL eat memory
CVE-2026-95690 is a memory-consumption flaw in how OpenSSL reassembles DTLS handshake messages. Crafted out-of-sequence handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message. The result is that a small amount of wire data consumes a large amount of memory. The story metadata rates the severity as medium, but NVD gives no CVSS score or vector.
How the fragment reassembly buffers get inflated
The attacker sends the crafted DTLS handshake fragments over the network, out of sequence. OpenSSL buffers each message while it waits for the missing pieces, and each buffered message gets a buffer sized for the whole message. That mismatch between what the attacker sends and what OpenSSL reserves is what makes the attack cheap.
Affected versions and exploitation status are not listed
According to NVD, the record is still marked "Awaiting Analysis" and does not list affected versions. The flaw sits in DTLS handshake handling, so services that use DTLS through OpenSSL are the ones to look at first. The sources do not say whether the flaw is being exploited, so its exploitation status is unknown.
No fixed OpenSSL release is known yet
No fixed version has been published in the sources, so there is nothing to update to yet. The NVD record lists OpenSSL GitHub pull requests 33620 and 33729 as references. Teams running services that use DTLS through OpenSSL should check them now and revisit the NVD entry for version data once it is filled in.
What NVD has not published yet
The record gives no workaround, no disclosure or patch dates, and no statement on server versus client exposure.
Sources
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].
Discussion