<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T13:49:12.422412+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-407006</id>
    <title>EUVD-2026-407006</title>
    <updated>2026-11-17T13:49:12.424131+00:00</updated>
    <content>EUVD-2026-407006</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-407006"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-24mq-4vc6-2prf</id>
    <title>GHSA-24mq-4vc6-2prf — mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input</title>
    <updated>2026-11-17T13:49:12.424163+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: mail-parser</p>
<p>### Impact</p>
<p>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.</p>
<p>**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.</p>
<p>*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`).</p>
<p>```python
import mailparser
mailparser.parse_from_string("Parse: x\r\n\r\n").mail_json
# 4.6.1 -&gt; TypeError: Object of type method is not JSON serializable
# 4.6.2 -&gt; {"parse": "x", "has_defects": false}
```</p>
<p>*Header carrying 8-bit bytes* (CWE-248). For a header containing raw 8-bit bytes, Python'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.</p>
<p>```python
import mailparser
mailparser.parse_from_bytes(b"Subject: caf\xe9\r\n\r\nbody\r\n…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-24mq-4vc6-2prf"/>
  </entry>
</feed>
