<?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://vulnerability.circl.lu</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, 01 Oct 2026 21:49:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-7383 — Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-7383</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: A signed integer overflow when sizing the destination
buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap
buffer overflow.&lt;/p&gt;
&lt;p&gt;Impact summary: A heap buffer overflow may lead to a crash or possibly
attacker controlled code execution or other undefined behaviour.&lt;/p&gt;
&lt;p&gt;In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination
size for Unicode output is computed in a signed int: by left shift
of the input character count for BMPSTRING (UTF-16) and
UNIVERSALSTRING (UTF-32), and by summing per-character byte counts
for UTF8STRING. The calculation overflows when the input reaches
around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30
characters) the size wraps to zero, OPENSSL_malloc(1) is called, and
the subsequent character copy writes several gigabytes past the
one-byte allocation.&lt;/p&gt;
&lt;p&gt;X.509 certificate processing routes through ASN1_STRING_set_by_NID(),
whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID
size limits cap the input length; no network protocol or
certificate-handling path in OpenSSL exercises the overflow.
Triggering the bug requires an application that calls
ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers
a custom string type via ASN1_STRING_TABLE_add(), with
attacker-controlled input on the order of half a gigabyte or more.
For these reasons this issue was assigned Low severity.&lt;/p&gt;
&lt;p&gt;The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by
this issue, as the affected code is…&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: A signed integer overflow when sizing the destination
buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap
buffer overflow.&lt;/p&gt;
&lt;p&gt;Impact summary: A heap buffer overflow may lead to a crash or possibly
attacker controlled code execution or other undefined behaviour.&lt;/p&gt;
&lt;p&gt;In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination
size for Unicode output is computed in a signed int: by left shift
of the input character count for BMPSTRING (UTF-16) and
UNIVERSALSTRING (UTF-32), and by summing per-character byte counts
for UTF8STRING. The calculation overflows when the input reaches
around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30
characters) the size wraps to zero, OPENSSL_malloc(1) is called, and
the subsequent character copy writes several gigabytes past the
one-byte allocation.&lt;/p&gt;
&lt;p&gt;X.509 certificate processing routes through ASN1_STRING_set_by_NID(),
whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID
size limits cap the input length; no network protocol or
certificate-handling path in OpenSSL exercises the overflow.
Triggering the bug requires an application that calls
ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers
a custom string type via ASN1_STRING_TABLE_add(), with
attacker-controlled input on the order of half a gigabyte or more.
For these reasons this issue was assigned Low severity.&lt;/p&gt;
&lt;p&gt;The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by
this issue, as the affected code is…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-7383</guid>
    </item>
    <item>
      <title>USN-8414-1 — openssl vulnerabilities</title>
      <link>https://vulnerability.circl.lu/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://vulnerability.circl.lu/vuln/usn-8414-1</guid>
    </item>
  </channel>
</rss>
