<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:44:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-408640</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-408640</link>
      <description>EUVD-2026-408640</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-408640</guid>
    </item>
    <item>
      <title>fkie_cve-2026-95690</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-95690</link>
      <description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;CWE: CWE-770: Allocation of Resources Without Limits or Throttling&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A single connection can then hold roughly 1.4MB of buffers from about 156
bytes on the wire. Because the nu…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;CWE: CWE-770: Allocation of Resources Without Limits or Throttling&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A single connection can then hold roughly 1.4MB of buffers from about 156
bytes on the wire. Because the nu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-95690</guid>
    </item>
    <item>
      <title>GHSA-g3cx-p9rc-jf32</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g3cx-p9rc-jf32</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g3cx-p9rc-jf32</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-95690 — Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassemb…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-95690</link>
      <description>msrc_CVE-2026-95690</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-95690</guid>
    </item>
    <item>
      <title>RHSA-2026:79719 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:79719</link>
      <description>&lt;p&gt;openssl: openssl: Denial of Service via out-of-bounds read during TLS key-share processing openssl: OpenSSL: Denial of Service via NULL pointer dereference during DANE TLSA record processing openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection openssl: OpenSSL: Message authentication bypass via zero-length AAD update openssl: openssl: Denial of service via crafted out-of-sequence DTLS handshake fragments openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV openssl: OpenSSL: Denial of Service via unbounded QUIC frame queueing openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption openssl: openssl: Out-of-bounds write via integer overflow in EVP_EncodeBlock() openssl: openssl: Denial of Service via crafted CMS or PKCS#7 SignedData message openssl: openssl: Denial of Service via memory leak in QUIC stream handling&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;openssl: openssl: Denial of Service via out-of-bounds read during TLS key-share processing openssl: OpenSSL: Denial of Service via NULL pointer dereference during DANE TLSA record processing openssl: openssl: Information disclosure via uninitialized memory in QUIC peer detection openssl: OpenSSL: Message authentication bypass via zero-length AAD update openssl: openssl: Denial of service via crafted out-of-sequence DTLS handshake fragments openssl: openssl: Denial of Service via overlapping QUIC CRYPTO frame processing openssl: OpenSSL: Denial of Service via out-of-bounds read in AES-GCM-SIV openssl: OpenSSL: Denial of Service via unbounded QUIC frame queueing openssl: openssl: Denial of Service via crafted EC certificate in CMS encryption openssl: openssl: Out-of-bounds write via integer overflow in EVP_EncodeBlock() openssl: openssl: Denial of Service via crafted CMS or PKCS#7 SignedData message openssl: openssl: Denial of Service via memory leak in QUIC stream handling&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:79719</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-95690</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-95690</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: openssl, Ubuntu:Pro:16.04:LTS: openssl, Ubuntu:Pro:16.04:LTS: edk2, Ubuntu:Pro:16.04:LTS: nodejs, Ubuntu:Pro:FIPS-updates:16.04:LTS: openssl, Ubuntu:Pro:FIPS:16.04:LTS: openssl, Ubuntu:Pro:18.04:LTS: openssl, Ubuntu:Pro:18.04:LTS: openssl1.0, Ubuntu:Pro:18.04:LTS: edk2, Ubuntu:Pro:18.04:LTS: nodejs and 22 more&lt;/p&gt;
&lt;p&gt;(Receiving crafted out-of-sequence DTLS handshake fragments may cause O ...)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: openssl, Ubuntu:Pro:16.04:LTS: openssl, Ubuntu:Pro:16.04:LTS: edk2, Ubuntu:Pro:16.04:LTS: nodejs, Ubuntu:Pro:FIPS-updates:16.04:LTS: openssl, Ubuntu:Pro:FIPS:16.04:LTS: openssl, Ubuntu:Pro:18.04:LTS: openssl, Ubuntu:Pro:18.04:LTS: openssl1.0, Ubuntu:Pro:18.04:LTS: edk2, Ubuntu:Pro:18.04:LTS: nodejs and 22 more&lt;/p&gt;
&lt;p&gt;(Receiving crafted out-of-sequence DTLS handshake fragments may cause O ...)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-95690</guid>
    </item>
  </channel>
</rss>
