<?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>Wed, 07 Oct 2026 03:21:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-47088</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-47088</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; cyrusimap Cyrus IMAP&lt;/p&gt;
&lt;p&gt;An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is heap exposure in nested MIME comment parsing. An authenticated IMAP user could craft an email message containing an RFC 822 comment ending with a backslash. When parsing the message, the server would read past the message&amp;#39;s end in memory, and read into the heap, returning the read content to the user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; cyrusimap Cyrus IMAP&lt;/p&gt;
&lt;p&gt;An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is heap exposure in nested MIME comment parsing. An authenticated IMAP user could craft an email message containing an RFC 822 comment ending with a backslash. When parsing the message, the server would read past the message&amp;#39;s end in memory, and read into the heap, returning the read content to the user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-47088</guid>
    </item>
  </channel>
</rss>
