cve.bz

CVE-2026-95690 Excessive Memory Allocation in DTLS Handshake Message Reassembly

5.3 mediumEPSS 0.3%

Medium (5.3) in openssl openssl. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-770 Allocation of Resources Without Limits or Throttling
CWE-400 Uncontrolled Resource Consumption
Published
Modified
Assigned by
openssl (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-95690 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95690?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95690?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95690 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenSSLfrom 4.1.0 before 4.1.1
OpenSSLfrom 4.0.0 before 4.0.4
OpenSSLfrom 3.5.0 before 3.5.10
OpenSSLfrom 3.0.0 before 3.0.24
OpenSSLfrom 1.1.1 before 1.1.1zk
OpenSSLfrom 1.0.2 before 1.0.2zt

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14opensslno fix listedDEBIAN-CVE-2026-95690
Ubuntu22.04:LTS, 24.04:LTS, Pro:20.04:LTSedk2, opensslno fix listedUBUNTU-CVE-2026-95690
Ubuntu26.04:LTS, 26.10edk2, openssl, edk2-hweno fix listedUBUNTU-CVE-2026-95690
UbuntuPro:14.04:LTS, Pro:FIPS-updates:16.04:LTS, Pro:FIPS-updates:18.04:LTS and 4 moreopensslno fix listedUBUNTU-CVE-2026-95690
UbuntuPro:16.04:LTSedk2, nodejs, opensslno fix listedUBUNTU-CVE-2026-95690
UbuntuPro:18.04:LTSedk2, nodejs, openssl and 1 moreno fix listedUBUNTU-CVE-2026-95690
UbuntuPro:22.04:LTSnodejsno fix listedUBUNTU-CVE-2026-95690
UbuntuPro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:22.04:LTSopenssl, openssl-fipsno fix listedUBUNTU-CVE-2026-95690
UbuntuPro:FIPS-updates:24.04:LTSopenssl-fipsno fix listedUBUNTU-CVE-2026-95690
Azure Linux3cloud-hypervisorno fix listedAZL-115754
Azure Linux3edk2no fix listedAZL-115790
Azure Linux3kata-containersno fix listedAZL-115805
Azure Linux3opensslno fix listedAZL-115841
Azure Linux3openssl-fips-providerno fix listedAZL-115274
Azure Linux3openvmmno fix listedAZL-115859
Azure Linux3qemuno fix listedAZL-115868
Azure Linux3rustno fix listedAZL-115877 AZL-115904
Alpaquita23, 25, streamopensslno fix listedBELL-CVE-2026-95690
BellSoft Hardened Containers23, 25, streamopensslno fix listedBELL-CVE-2026-95690

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita · BellSoft Hardened Containers.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

History

  1. Scored 5.3 medium

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON