CVE-2026-95690 (GCVE-0-2026-95690)

Vulnerability from cvelistv5 – Published: 2026-11-18 11:44 – Updated: 2026-11-20 11:19
VLAI
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.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 13:50 UTC
CWE
  • CWE-770 - Allocation of Resources Without Limits or Throttling
  • CWE-400 - Uncontrolled Resource Consumption
Assigner
openssl CNA
Impacted products
Vendor Product Version
OpenSSL OpenSSL Affected: 4.1.0 , < 4.1.1 (semver)
Affected: 4.0.0 , < 4.0.4 (semver)
Affected: 3.5.0 , < 3.5.10 (semver)
Affected: 3.0.0 , < 3.0.24 (semver)
Affected: 1.1.1 , < 1.1.1zk (custom)
Affected: 1.0.2 , < 1.0.2zt (custom)
Create a notification for this product.
Date Public
2026-11-20 11:05
Show details on NVD website

{
  "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-19",
      "epss": "0.00351",
      "percentile": "0.29355"
    },
    "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"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    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.