<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 05:57:37 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:67154 — Important: openssl security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:67154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: openssl, AlmaLinux:10: openssl-devel, AlmaLinux:10: openssl-libs, AlmaLinux:10: openssl-perl&lt;/p&gt;
&lt;p&gt;OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)
  * openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)
  * openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
  * openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)
  * openssl: RPK server signature algorithm selection can dereference a missing certificate (CVE-2026-14457)
  * openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)
  * openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)
  * openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)
  * openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* openssl: HollowByte remote memory-exhaustion DoS fix may be missing [AlmaLinux 10.2.z] (JIRA:AlmaLinux-212362)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: openssl, AlmaLinux:10: openssl-devel, AlmaLinux:10: openssl-libs, AlmaLinux:10: openssl-perl&lt;/p&gt;
&lt;p&gt;OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)
  * openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)
  * openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
  * openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)
  * openssl: RPK server signature algorithm selection can dereference a missing certificate (CVE-2026-14457)
  * openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)
  * openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)
  * openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)
  * openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* openssl: HollowByte remote memory-exhaustion DoS fix may be missing [AlmaLinux 10.2.z] (JIRA:AlmaLinux-212362)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:67154</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-63072</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-63072</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: openssl, Alpaquita:25: openssl, Alpaquita:stream: openssl, BellSoft Hardened Containers:23: openssl, BellSoft Hardened Containers:25: openssl, BellSoft Hardened Containers:stream: openssl&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: openssl, Alpaquita:25: openssl, Alpaquita:stream: openssl, BellSoft Hardened Containers:23: openssl, BellSoft Hardened Containers:25: openssl, BellSoft Hardened Containers:stream: openssl&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-63072</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1079 — De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles permettent à un attaquant de provoquer un déni de s…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1079</link>
      <description>certfr-2026-avi-1079</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1079</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-VK14120 — Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based
on querying the unwrapped key size, but…</title>
      <link>https://127.0.0.1:10001/vuln/cleanstart-2026-vk14120</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: miniforge3&lt;/p&gt;
&lt;p&gt;CVE-2026-63072 affects multiple packages. Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: miniforge3&lt;/p&gt;
&lt;p&gt;CVE-2026-63072 affects multiple packages. Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cleanstart-2026-vk14120</guid>
    </item>
    <item>
      <title>OESA-2026-3819 — compat-openssl11 security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3819</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: compat-openssl11&lt;/p&gt;
&lt;p&gt;OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;Issue summary: Receiving a DTLS record for a future epoch while a handshake
is in progress causes OpenSSL to buffer far more memory than the record
itself requires.&lt;/p&gt;
&lt;p&gt;Impact summary: A peer can use a small amount of network traffic to make an
OpenSSL DTLS endpoint retain a disproportionately large amount of memory,
which may lead to a Denial of Service.&lt;/p&gt;
&lt;p&gt;CWE: CWE-405: Asymmetric Resource Consumption (Amplification)&lt;/p&gt;
&lt;p&gt;Description: While a DTLS handshake is in progress, a peer may legitimately
have already moved on to the next epoch (for example, having sent its
ChangeCipherSpec and Finished messages) before the local endpoint has
processed the same transition, typically because of reordering on the
underlying UDP transport. OpenSSL buffers such early records so that they
can be processed once the local endpoint catches up.&lt;/p&gt;
&lt;p&gt;Buffering a record currently retains the entire read buffer it arrived in,
which is sized to hold the largest possible DTLS record (around 16
kilobytes), rather than just the bytes that make up the record itself. Up
to 100 such records may be buffered per connection. As a result, a peer
that sends a stream of small forged records claiming to belong to the next
epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of
memory, despite sending only a small fraction of that amount…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: compat-openssl11&lt;/p&gt;
&lt;p&gt;OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;Issue summary: Receiving a DTLS record for a future epoch while a handshake
is in progress causes OpenSSL to buffer far more memory than the record
itself requires.&lt;/p&gt;
&lt;p&gt;Impact summary: A peer can use a small amount of network traffic to make an
OpenSSL DTLS endpoint retain a disproportionately large amount of memory,
which may lead to a Denial of Service.&lt;/p&gt;
&lt;p&gt;CWE: CWE-405: Asymmetric Resource Consumption (Amplification)&lt;/p&gt;
&lt;p&gt;Description: While a DTLS handshake is in progress, a peer may legitimately
have already moved on to the next epoch (for example, having sent its
ChangeCipherSpec and Finished messages) before the local endpoint has
processed the same transition, typically because of reordering on the
underlying UDP transport. OpenSSL buffers such early records so that they
can be processed once the local endpoint catches up.&lt;/p&gt;
&lt;p&gt;Buffering a record currently retains the entire read buffer it arrived in,
which is sized to hold the largest possible DTLS record (around 16
kilobytes), rather than just the bytes that make up the record itself. Up
to 100 such records may be buffered per connection. As a result, a peer
that sends a stream of small forged records claiming to belong to the next
epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of
memory, despite sending only a small fraction of that amount…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3819</guid>
    </item>
    <item>
      <title>RLSA-2026:67154 — Important: openssl security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:67154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: openssl-perl, Rocky Linux:10: openssl-libs-debuginfo, Rocky Linux:10: openssl-libs, Rocky Linux:10: openssl, Rocky Linux:10: openssl-devel, Rocky Linux:10: openssl-debuginfo, Rocky Linux:10: openssl-debugsource&lt;/p&gt;
&lt;p&gt;OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)&lt;/p&gt;
&lt;p&gt;* openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)&lt;/p&gt;
&lt;p&gt;* openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)&lt;/p&gt;
&lt;p&gt;* openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)&lt;/p&gt;
&lt;p&gt;* openssl: RPK server signature algorithm selection can dereference a missing certificate (CVE-2026-14457)&lt;/p&gt;
&lt;p&gt;* openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)&lt;/p&gt;
&lt;p&gt;* openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)&lt;/p&gt;
&lt;p&gt;* openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)&lt;/p&gt;
&lt;p&gt;* openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* openssl: HollowByte remote memory-exhaustion DoS fix may be missing [Rocky Linux 10.2.z] (JIRA:Rocky Linux-212362)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: openssl-perl, Rocky Linux:10: openssl-libs-debuginfo, Rocky Linux:10: openssl-libs, Rocky Linux:10: openssl, Rocky Linux:10: openssl-devel, Rocky Linux:10: openssl-debuginfo, Rocky Linux:10: openssl-debugsource&lt;/p&gt;
&lt;p&gt;OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* openssl: OpenSSL: Denial of Service via unbounded memory growth in QUIC server (CVE-2026-14456)&lt;/p&gt;
&lt;p&gt;* openssl: QUIC server may trigger double free when processing INITIAL packet (CVE-2026-18798)&lt;/p&gt;
&lt;p&gt;* openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)&lt;/p&gt;
&lt;p&gt;* openssl: invalid pointer dereference in CMP server via crafted protectionAlg (CVE-2026-63076)&lt;/p&gt;
&lt;p&gt;* openssl: RPK server signature algorithm selection can dereference a missing certificate (CVE-2026-14457)&lt;/p&gt;
&lt;p&gt;* openssl: excessive memory use buffering DTLS records for a future epoch (CVE-2026-54874)&lt;/p&gt;
&lt;p&gt;* openssl: untrusted sender DN used as format string in CMP response validation (CVE-2026-63073)&lt;/p&gt;
&lt;p&gt;* openssl: CMP indefinite cache growth of ExtraCerts (CVE-2026-63074)&lt;/p&gt;
&lt;p&gt;* openssl: QUIC ACK-only packet retention can cause memory exhaustion (CVE-2026-63075)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* openssl: HollowByte remote memory-exhaustion DoS fix may be missing [Rocky Linux 10.2.z] (JIRA:Rocky Linux-212362)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:67154</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63072</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63072</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: 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, Ubuntu:Pro:FIPS-updates:18.04:LTS: openssl and 20 more&lt;/p&gt;
&lt;p&gt;Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient&amp;#39;s private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIP…&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: 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, Ubuntu:Pro:FIPS-updates:18.04:LTS: openssl and 20 more&lt;/p&gt;
&lt;p&gt;Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient&amp;#39;s private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIP…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63072</guid>
    </item>
  </channel>
</rss>
