<?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>Thu, 15 Oct 2026 15:12:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45445 — AES-OCB IV Ignored on EVP_Cipher() Path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-45445</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: When an application drives an AES-OCB context through the
public EVP_Cipher() one-shot interface, the application-supplied
initialisation vector (IV) is silently discarded.&lt;/p&gt;
&lt;p&gt;Impact summary: Every message encrypted under the same key uses the
same effective nonce regardless of the IV supplied by the caller,
resulting in (key, nonce) reuse and loss of confidentiality.  If the
same code path is used to compute the authentication tag, the tag
depends only on the (key, IV) pair and not on the plaintext or
ciphertext, allowing universal forgery of arbitrary ciphertext from a
single captured message.&lt;/p&gt;
&lt;p&gt;OpenSSL provides two ways to drive a cipher: the documented streaming
interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level
one-shot, EVP_Cipher(), whose documentation explicitly recommends
against use by applications in favour of EVP_CipherUpdate() and
EVP_CipherFinal_ex().  The OCB provider&amp;#39;s streaming handler flushes
the application-supplied IV into the OCB context before processing
data; the one-shot handler did not.  Every call to EVP_Cipher() on an
AES-OCB context therefore ran with the all-zero key-derived offset
state left by cipher initialisation, regardless of the caller&amp;#39;s IV.&lt;/p&gt;
&lt;p&gt;If EVP_EncryptFinal_ex() is subsequently used to obtain the
authentication tag, the deferred IV setup runs at that point and
clears the running checksum that should have been accumulated over the
plaintext.  The resulting tag is a function of (key, IV) only and
verifies ag…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: When an application drives an AES-OCB context through the
public EVP_Cipher() one-shot interface, the application-supplied
initialisation vector (IV) is silently discarded.&lt;/p&gt;
&lt;p&gt;Impact summary: Every message encrypted under the same key uses the
same effective nonce regardless of the IV supplied by the caller,
resulting in (key, nonce) reuse and loss of confidentiality.  If the
same code path is used to compute the authentication tag, the tag
depends only on the (key, IV) pair and not on the plaintext or
ciphertext, allowing universal forgery of arbitrary ciphertext from a
single captured message.&lt;/p&gt;
&lt;p&gt;OpenSSL provides two ways to drive a cipher: the documented streaming
interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level
one-shot, EVP_Cipher(), whose documentation explicitly recommends
against use by applications in favour of EVP_CipherUpdate() and
EVP_CipherFinal_ex().  The OCB provider&amp;#39;s streaming handler flushes
the application-supplied IV into the OCB context before processing
data; the one-shot handler did not.  Every call to EVP_Cipher() on an
AES-OCB context therefore ran with the all-zero key-derived offset
state left by cipher initialisation, regardless of the caller&amp;#39;s IV.&lt;/p&gt;
&lt;p&gt;If EVP_EncryptFinal_ex() is subsequently used to obtain the
authentication tag, the deferred IV setup runs at that point and
clears the running checksum that should have been accumulated over the
plaintext.  The resulting tag is a function of (key, IV) only and
verifies ag…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-45445</guid>
    </item>
    <item>
      <title>USN-8414-1 — openssl vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8414-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: openssl, Ubuntu:24.04:LTS: openssl, Ubuntu:25.10: openssl, Ubuntu:26.04:LTS: openssl&lt;/p&gt;
&lt;p&gt;Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1
content parsing. An attacker could possibly use this issue to cause OpenSSL
to crash, resulting in a denial of service, or obtain sensitive
information. (CVE-2026-34180)&lt;/p&gt;
&lt;p&gt;Pavol Zacik and Alex Gaynor discovered that OpenSSL incorrectly accepted
PKCS#12 files with short HMAC keys when using PBMAC1. An attacker could
possibly use this issue to bypass integrity checks. This issue only
affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34181)&lt;/p&gt;
&lt;p&gt;Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could
accept forged CMS AuthEnvelopedData messages. An attacker could possibly
use this issue to bypass message authentication checks. (CVE-2026-34182)&lt;/p&gt;
&lt;p&gt;Abhinav Agarwal discovered that OpenSSL had unbounded memory growth in the
QUIC PATH_CHALLENGE handler. A remote attacker could possibly use this
issue to cause OpenSSL to use excessive resources, leading to a denial of
service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS.
(CVE-2026-34183)&lt;/p&gt;
&lt;p&gt;Sunwoo Lee, Hyuk Lim, and Seunghyun Yoon discovered that OpenSSL had a NULL
pointer dereference in QUIC server initial packet handling. A remote
attacker could possibly use this issue to cause OpenSSL to crash, resulting
in a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu
26.04 LTS. (CVE-2026-42764)&lt;/p&gt;
&lt;p&gt;Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan
Zhang discovered that OpenSSL had a possible NULL derefe…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: openssl, Ubuntu:24.04:LTS: openssl, Ubuntu:25.10: openssl, Ubuntu:26.04:LTS: openssl&lt;/p&gt;
&lt;p&gt;Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1
content parsing. An attacker could possibly use this issue to cause OpenSSL
to crash, resulting in a denial of service, or obtain sensitive
information. (CVE-2026-34180)&lt;/p&gt;
&lt;p&gt;Pavol Zacik and Alex Gaynor discovered that OpenSSL incorrectly accepted
PKCS#12 files with short HMAC keys when using PBMAC1. An attacker could
possibly use this issue to bypass integrity checks. This issue only
affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34181)&lt;/p&gt;
&lt;p&gt;Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could
accept forged CMS AuthEnvelopedData messages. An attacker could possibly
use this issue to bypass message authentication checks. (CVE-2026-34182)&lt;/p&gt;
&lt;p&gt;Abhinav Agarwal discovered that OpenSSL had unbounded memory growth in the
QUIC PATH_CHALLENGE handler. A remote attacker could possibly use this
issue to cause OpenSSL to use excessive resources, leading to a denial of
service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS.
(CVE-2026-34183)&lt;/p&gt;
&lt;p&gt;Sunwoo Lee, Hyuk Lim, and Seunghyun Yoon discovered that OpenSSL had a NULL
pointer dereference in QUIC server initial packet handling. A remote
attacker could possibly use this issue to cause OpenSSL to crash, resulting
in a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu
26.04 LTS. (CVE-2026-42764)&lt;/p&gt;
&lt;p&gt;Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan
Zhang discovered that OpenSSL had a possible NULL derefe…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8414-1</guid>
    </item>
  </channel>
</rss>
