<?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>Sat, 03 Oct 2026 02:12:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-36632</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-36632</link>
      <description>&lt;p&gt;The legacy email.utils.parseaddr function in Python through 3.11.4 allows attackers to trigger &amp;#34;RecursionError: maximum recursion depth exceeded while calling a Python object&amp;#34; via a crafted argument. This argument is plausibly an untrusted value from an application&amp;#39;s input data that was supposed to contain a name and an e-mail address. NOTE: email.utils.parseaddr is categorized as a Legacy API in the documentation of the Python email package. Applications should instead use the email.parser.BytesParser or email.parser.Parser class. NOTE: the vendor&amp;#39;s perspective is that this is neither a vulnerability nor a bug. The email package is intended to have size limits and to throw an exception when limits are exceeded; they were exceeded by the example demonstration code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The legacy email.utils.parseaddr function in Python through 3.11.4 allows attackers to trigger &amp;#34;RecursionError: maximum recursion depth exceeded while calling a Python object&amp;#34; via a crafted argument. This argument is plausibly an untrusted value from an application&amp;#39;s input data that was supposed to contain a name and an e-mail address. NOTE: email.utils.parseaddr is categorized as a Legacy API in the documentation of the Python email package. Applications should instead use the email.parser.BytesParser or email.parser.Parser class. NOTE: the vendor&amp;#39;s perspective is that this is neither a vulnerability nor a bug. The email package is intended to have size limits and to throw an exception when limits are exceeded; they were exceeded by the example demonstration code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-36632</guid>
    </item>
  </channel>
</rss>
