{"id":"DHI-mkpj-fjqt-t4vy-4syf","summary":"Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may","details":"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.","modified":"2026-11-21T20:45:03.068281284Z","published":"2026-11-19T00:29:06Z","upstream":["CVE-2026-95690"],"database_specific":{"coverage":"partial","coverage_exclusions":["legacy_package_image_owner"]},"references":[{"type":"ADVISORY","url":"https://scout.docker.com/v/DHI-mkpj-fjqt-t4vy-4syf"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-95690"},{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2026-95690"},{"type":"ADVISORY","url":"https://ubuntu.com/security/CVE-2026-95690"},{"type":"ADVISORY","url":"http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-95690"},{"type":"FIX","url":"https://github.com/openssl/openssl/pull/33729"},{"type":"FIX","url":"https://github.com/openssl/openssl/pull/33620"}],"affected":[{"package":{"name":"openssl","ecosystem":"Docker Hardened Images:Debian:13","purl":"pkg:deb/dhi/openssl"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.5.5-1~deb13u2dhi0","3.5.6-1~deb13u1+dhi0","3.5.6-1~deb13u1+dhi1","3.5.6-1~deb13u1+dhi2","3.5.6-1~deb13u1+fips+dhi0","3.5.6-1~deb13u1+fips+dhi1","3.5.6-1~deb13u1+fips+dhi2","3.5.6-1~deb13u1dhi0","3.5.6-1~deb13u2+dhi0","3.5.6-1~deb13u2+dhi1","3.5.6-1~deb13u2+dhi2","3.5.6-1~deb13u2+dhi3","3.5.6-1~deb13u2+fips+dhi0","3.5.6-1~deb13u2+fips+dhi1","3.5.7-1~deb13u2+dhi0","3.5.7-1~deb13u2+dhi1","3.5.7-1~deb13u2+fips+dhi0","3.5.7-1~deb13u3+dhi0","3.5.7-1~deb13u3+dhi1","3.5.7-1~deb13u3+dhi2","3.5.7-1~deb13u3+dhi3","3.5.7-1~deb13u3+fips+dhi0","3.5.9-1~deb13u1+dhi0","3.5.9-1~deb13u1+fips+dhi0"],"database_specific":{"owner_kind":"HSP","source":"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-mkpj-fjqt-t4vy-4syf.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"}]}