<?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:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407009</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407009</link>
      <description>EUVD-2026-407009</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407009</guid>
    </item>
    <item>
      <title>GHSA-72px-j8gh-p79x — mail-parser: Sender IP address spoofing in get_server_ipaddress()</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-72px-j8gh-p79x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mail-parser&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in **4.6.2**. Upgrade with `pip install --upgrade mail-parser`.&lt;/p&gt;
&lt;p&gt;Candidate addresses are now selected by position, not by appearance — a bracketed address
the sender wrote is byte-identical to one the MTA wrote, so no amount of pattern matching
can tell them apart:&lt;/p&gt;
&lt;p&gt;- the first token of the `from` clause is the HELO name, whatever its shape, and is never a
  candidate;
- an explicit HELO marker inside a comment group is sender text and is excluded;
- a candidate must sit inside a `(` / `[` group;
- IPv4 and IPv6 matches are merged positionally, never family-first;
- the walk stops at the first trusted hop naming no address, rather than continuing into
  sender-written headers.&lt;/p&gt;
&lt;p&gt;The IPv6 pattern was corrected to skip the `IPv6:` tag and to prefer the longest valid form.&lt;/p&gt;
&lt;p&gt;**Behaviour change.** `get_server_ipaddress()` now returns `None` rather than an unreliable
value in two cases that previously returned an address: a `from` clause consisting of a bare
address with no HELO marker (indistinguishable from `EHLO &amp;lt;that address&amp;gt;`), and a trusted hop
naming no address at all. Callers must handle `None`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;None within mail-parser. Callers who cannot upgrade should not treat the return value of
`get_server_ipaddress()` as trustworthy, and should derive sender attribution from an
authenticated signal instead — the MTA&amp;#39;s own logs, or SPF/DKIM/DMARC results computed
outside this library.&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;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in **4.6.2**. Upgrade with `pip install --upgrade mail-parser`.&lt;/p&gt;
&lt;p&gt;Candidate addresses are now selected by position, not by appearance — a bracketed address
the sender wrote is byte-identical to one the MTA wrote, so no amount of pattern matching
can tell them apart:&lt;/p&gt;
&lt;p&gt;- the first token of the `from` clause is the HELO name, whatever its shape, and is never a
  candidate;
- an explicit HELO marker inside a comment group is sender text and is excluded;
- a candidate must sit inside a `(` / `[` group;
- IPv4 and IPv6 matches are merged positionally, never family-first;
- the walk stops at the first trusted hop naming no address, rather than continuing into
  sender-written headers.&lt;/p&gt;
&lt;p&gt;The IPv6 pattern was corrected to skip the `IPv6:` tag and to prefer the longest valid form.&lt;/p&gt;
&lt;p&gt;**Behaviour change.** `get_server_ipaddress()` now returns `None` rather than an unreliable
value in two cases that previously returned an address: a `from` clause consisting of a bare
address with no HELO marker (indistinguishable from `EHLO &amp;lt;that address&amp;gt;`), and a trusted hop
naming no address at all. Callers must handle `None`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;None within mail-parser. Callers who cannot upgrade should not treat the return value of
`get_server_ipaddress()` as trustworthy, and should derive sender attribution from an
authenticated signal instead — the MTA&amp;#39;s own logs, or SPF/DKIM/DMARC results computed
outside this library.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-72px-j8gh-p79x</guid>
    </item>
  </channel>
</rss>
