CVE-2026-95690 (GCVE-0-2026-95690)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:44 – Updated: 2026-11-20 11:19
VLAI
EPSS
VEX
Title
Excessive Memory Allocation in DTLS Handshake Message Reassembly
Summary
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
5.3 (Medium)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 13:50 UTC
CWE
Assigner
References
2 references
Impacted products
Date Public
2026-11-20 11:05
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95690",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T13:50:26.611679Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400 Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T15:23:34.371Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Joel Sing"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Ryan Hooper"
}
],
"datePublic": "2026-11-20T11:05:22.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may\u003cbr\u003ecause OpenSSL to allocate a full message-length reassembly buffer for each\u003cbr\u003ebuffered message, so a small amount of wire data consumes a large amount of\u003cbr\u003ememory.\u003cbr\u003e\u003cbr\u003eImpact summary: A remote attacker can send a few small crafted DTLS handshake\u003cbr\u003efragments to make a DTLS server or client allocate well over a megabyte of\u003cbr\u003ememory per connection, which may lead to memory exhaustion and Denial of\u003cbr\u003eService if many connections are made.\u003cbr\u003e\u003cbr\u003eCWE: CWE-770: Allocation of Resources Without Limits or Throttling\u003cbr\u003e\u003cbr\u003eDescription: DTLS handshake messages can arrive out of order and fragmented,\u003cbr\u003eso OpenSSL buffers fragments of up to ten out-of-sequence messages until\u003cbr\u003ereassembly is possible. When the first fragment of a new message arrives,\u003cbr\u003eOpenSSL allocates a buffer sized to the full message length declared in the\u003cbr\u003efragment header, plus a reassembly bitmap, instead of storing only the bytes\u003cbr\u003eactually received. The declared length is capped by the maximum certificate\u003cbr\u003elist size, 128KB by default, and that cap applies to every handshake message\u003cbr\u003etype rather than only to Certificate messages.\u003cbr\u003e\u003cbr\u003eOnly DTLS endpoints reach this code. TLS, QUIC and applications that do not\u003cbr\u003euse DTLS are unaffected. An attacker sends fragments that declare a large\u003cbr\u003emessage length but carry almost no data, using up to ten distinct message\u003cbr\u003esequence numbers.\u003cbr\u003e\u003cbr\u003eA single connection can then hold roughly 1.4MB of buffers from about 156\u003cbr\u003ebytes on the wire. Because the number of buffered messages is capped, memory\u003cbr\u003eexhaustion requires many connections or many peers, which is why the severity\u003cbr\u003eis Low.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may\ncause OpenSSL to allocate a full message-length reassembly buffer for each\nbuffered message, so a small amount of wire data consumes a large amount of\nmemory.\n\nImpact summary: A remote attacker can send a few small crafted DTLS handshake\nfragments to make a DTLS server or client allocate well over a megabyte of\nmemory per connection, which may lead to memory exhaustion and Denial of\nService if many connections are made.\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: DTLS handshake messages can arrive out of order and fragmented,\nso OpenSSL buffers fragments of up to ten out-of-sequence messages until\nreassembly is possible. When the first fragment of a new message arrives,\nOpenSSL allocates a buffer sized to the full message length declared in the\nfragment header, plus a reassembly bitmap, instead of storing only the bytes\nactually received. The declared length is capped by the maximum certificate\nlist size, 128KB by default, and that cap applies to every handshake message\ntype rather than only to Certificate messages.\n\nOnly DTLS endpoints reach this code. TLS, QUIC and applications that do not\nuse DTLS are unaffected. An attacker sends fragments that declare a large\nmessage length but carry almost no data, using up to ten distinct message\nsequence numbers.\n\nA single connection can then hold roughly 1.4MB of buffers from about 156\nbytes on the wire. Because the number of buffered messages is capped, memory\nexhaustion requires many connections or many peers, which is why the severity\nis Low.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-770",
"description": "CWE-770 Allocation of Resources Without Limits or Throttling",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T11:19:59.821Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR for 4.1",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33620"
},
{
"name": "Fix PR for 4.0, 3.5",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33729"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Excessive Memory Allocation in DTLS Handshake Message Reassembly",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95690",
"datePublished": "2026-11-18T11:44:16.564Z",
"dateReserved": "2026-09-22T14:18:48.634Z",
"dateUpdated": "2026-11-20T11:19:59.821Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-95690",
"date": "2026-11-20",
"epss": "0.00351",
"percentile": "0.29495"
},
"microsoft_vex": {
"current_release_date": "2026-11-20T01:12:38.000Z",
"cve": "CVE-2026-95690",
"id": "msrc_CVE-2026-95690",
"initial_release_date": "2026-11-20T01:12:38.000Z",
"product_status:under_investigation": "6",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "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.",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-95690.json",
"version": "1"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"source": "openssl-security@openssl.org"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may\ncause OpenSSL to allocate a full message-length reassembly buffer for each\nbuffered message, so a small amount of wire data consumes a large amount of\nmemory.\n\nImpact summary: A remote attacker can send a few small crafted DTLS handshake\nfragments to make a DTLS server or client allocate well over a megabyte of\nmemory per connection, which may lead to memory exhaustion and Denial of\nService if many connections are made.\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: DTLS handshake messages can arrive out of order and fragmented,\nso OpenSSL buffers fragments of up to ten out-of-sequence messages until\nreassembly is possible. When the first fragment of a new message arrives,\nOpenSSL allocates a buffer sized to the full message length declared in the\nfragment header, plus a reassembly bitmap, instead of storing only the bytes\nactually received. The declared length is capped by the maximum certificate\nlist size, 128KB by default, and that cap applies to every handshake message\ntype rather than only to Certificate messages.\n\nOnly DTLS endpoints reach this code. TLS, QUIC and applications that do not\nuse DTLS are unaffected. An attacker sends fragments that declare a large\nmessage length but carry almost no data, using up to ten distinct message\nsequence numbers.\n\nA single connection can then hold roughly 1.4MB of buffers from about 156\nbytes on the wire. Because the number of buffered messages is capped, memory\nexhaustion requires many connections or many peers, which is why the severity\nis Low.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"id": "CVE-2026-95690",
"lastModified": "2026-11-20T12:18:25.127",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-95690",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T13:50:26.611679Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-18T12:17:24.037",
"references": [
{
"source": "openssl-security@openssl.org",
"url": "https://github.com/openssl/openssl/pull/33620"
},
{
"source": "openssl-security@openssl.org",
"url": "https://github.com/openssl/openssl/pull/33729"
}
],
"sourceIdentifier": "openssl-security@openssl.org",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-770"
}
],
"source": "openssl-security@openssl.org",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-400"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T17:48:01+00:00",
"cve": "CVE-2026-95690",
"id": "CVE-2026-95690",
"initial_release_date": "2026-11-18T11:44:16.564000+00:00",
"product_status:fixed": "50",
"product_status:known_affected": "48",
"product_status:known_not_affected": "147",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "openssl: openssl: Denial of service via crafted out-of-sequence DTLS handshake fragments",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-95690.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-19T01:02:03Z",
"cve": "CVE-2026-95690",
"id": "CVE-2026-95690",
"initial_release_date": "2026-11-19T01:02:03Z",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-95690",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-95690.json",
"version": "2"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95690",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T13:50:26.611679Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400 Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T13:50:19.287Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:44:16.564Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR for 4.1",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33620"
},
{
"name": "Fix PR for 4.0 and 3.5",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33729"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95690",
"datePublished": "2026-11-18T11:44:16.564Z",
"dateReserved": "2026-09-22T14:18:48.634Z",
"dateUpdated": "2026-11-18T15:23:34.371Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…