Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length
Source GCVE Database
Not known to be exploited · fixed in 4.1.1 : update OpenSSL when convenient.
Data as of 18 Nov 2026, 13:51 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.1.1, 4.0.4, 3.5.10 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A vulnerability in OpenSSL's DTLS implementation allows crafted out-of-sequence handshake fragments to cause excessive memory allocation. This occurs because OpenSSL allocates a full message-length reassembly buffer for each buffered message, leading to disproportionate memory consumption from a small amount of input data.