<?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>Tue, 17 Nov 2026 14:12:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407006</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407006</link>
      <description>EUVD-2026-407006</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407006</guid>
    </item>
    <item>
      <title>GHSA-24mq-4vc6-2prf — mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-24mq-4vc6-2prf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mail-parser&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Two effects, sharing the root cause of Advisory 1 — header names chosen by the sender were
resolved through Python attribute lookup and rewritten before lookup.&lt;/p&gt;
&lt;p&gt;**Uncaught exceptions.** A crafted message raises an exception that is *outside* the
`MailParser*` hierarchy, so a caller catching only mail-parser exceptions does not catch it
and the worker dies.&lt;/p&gt;
&lt;p&gt;*Header named after a method* (CWE-248, reported by @iam-niranjan). Python resolves real
class attributes before `__getattr__`, so a header named after a method put a bound method
object into the parsed mail dict. A 12-byte email is sufficient. Nine colliding names were
confirmed: `Parse`, `Message`, `Write_Attachments`, `From_File`, `From_File_Obj`,
`From_File_Msg`, `From_String`, `From_Bytes`, `Get_Server_Ipaddress`. Also reproducible from
the CLI (`mail-parser -f evil.eml -j`).&lt;/p&gt;
&lt;p&gt;```python
import mailparser
mailparser.parse_from_string(&amp;#34;Parse: x\r\n\r\n&amp;#34;).mail_json
# 4.6.1 -&amp;gt; TypeError: Object of type method is not JSON serializable
# 4.6.2 -&amp;gt; {&amp;#34;parse&amp;#34;: &amp;#34;x&amp;#34;, &amp;#34;has_defects&amp;#34;: false}
```&lt;/p&gt;
&lt;p&gt;*Header carrying 8-bit bytes* (CWE-248). For a header containing raw 8-bit bytes, Python&amp;#39;s
`compat32` policy returns an `email.header.Header` rather than a `str`, which the `_raw`
accessor passed straight to `json.dumps`. This fires on entirely benign non-ASCII mail via
`parse_from_bytes()`, the normal entry point for mail off the wire.&lt;/p&gt;
&lt;p&gt;```python
import mailparser
mailparser.parse_from_bytes(b&amp;#34;Subject: caf\xe9\r\n\r\nbody\r\n…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mail-parser&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Two effects, sharing the root cause of Advisory 1 — header names chosen by the sender were
resolved through Python attribute lookup and rewritten before lookup.&lt;/p&gt;
&lt;p&gt;**Uncaught exceptions.** A crafted message raises an exception that is *outside* the
`MailParser*` hierarchy, so a caller catching only mail-parser exceptions does not catch it
and the worker dies.&lt;/p&gt;
&lt;p&gt;*Header named after a method* (CWE-248, reported by @iam-niranjan). Python resolves real
class attributes before `__getattr__`, so a header named after a method put a bound method
object into the parsed mail dict. A 12-byte email is sufficient. Nine colliding names were
confirmed: `Parse`, `Message`, `Write_Attachments`, `From_File`, `From_File_Obj`,
`From_File_Msg`, `From_String`, `From_Bytes`, `Get_Server_Ipaddress`. Also reproducible from
the CLI (`mail-parser -f evil.eml -j`).&lt;/p&gt;
&lt;p&gt;```python
import mailparser
mailparser.parse_from_string(&amp;#34;Parse: x\r\n\r\n&amp;#34;).mail_json
# 4.6.1 -&amp;gt; TypeError: Object of type method is not JSON serializable
# 4.6.2 -&amp;gt; {&amp;#34;parse&amp;#34;: &amp;#34;x&amp;#34;, &amp;#34;has_defects&amp;#34;: false}
```&lt;/p&gt;
&lt;p&gt;*Header carrying 8-bit bytes* (CWE-248). For a header containing raw 8-bit bytes, Python&amp;#39;s
`compat32` policy returns an `email.header.Header` rather than a `str`, which the `_raw`
accessor passed straight to `json.dumps`. This fires on entirely benign non-ASCII mail via
`parse_from_bytes()`, the normal entry point for mail off the wire.&lt;/p&gt;
&lt;p&gt;```python
import mailparser
mailparser.parse_from_bytes(b&amp;#34;Subject: caf\xe9\r\n\r\nbody\r\n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-24mq-4vc6-2prf</guid>
    </item>
  </channel>
</rss>
