<?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 13:31:11 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407004</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407004</link>
      <description>EUVD-2026-407004</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407004</guid>
    </item>
    <item>
      <title>GHSA-r7w7-vpq8-c5vv — mail-parser is vulnerable to polynomial ReDoS in email header parsing</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r7w7-vpq8-c5vv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mail-parser&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Two regular expressions used while parsing email headers backtrack
polynomially on attacker-controlled input. Parsing a single small, well-formed
email can consume minutes to hours of CPU, denying service to any process that
parses untrusted mail.&lt;/p&gt;
&lt;p&gt;Both are reachable from an ordinary `parse_from_string()`, `parse_from_bytes()`
or `parse_from_file()` call — no special API, option, or malformed structure is
required by the victim.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**1. Address-header fallback regex (`src/mailparser/utils.py`)**&lt;/p&gt;
&lt;p&gt;`get_addresses()` falls back to `_ADDR_FALLBACK_RE` whenever
`email.utils.getaddresses(strict=True)` yields no usable address. The
alternative `([^&amp;lt;,]*?)\s*&amp;lt;([^&amp;gt;]+)&amp;gt;` overlaps a lazy quantifier with an adjacent
`\s*` — a space matches both. Driven by `finditer`, which retries at every
offset and rescans the remainder, matching degrades to **quadratic** on `&amp;lt;`
padding and **cubic** on whitespace padding.&lt;/p&gt;
&lt;p&gt;The fallback engages on the feature&amp;#39;s own happy path, e.g.
`From: alice@example.com &amp;lt;bob@example.com&amp;gt;`.&lt;/p&gt;
&lt;p&gt;Measured (4.6.0, CPython 3.14, macOS arm64; reproduced identically on Linux and
on CPython 3.9, 3.11, 3.12, 3.13):&lt;/p&gt;
&lt;p&gt;| Padding                | Parse time         |
| ---------------------- | ------------------ |
| valid address + 750 sp | 0.38 s             |
| + 1500 sp              | 2.97 s             |
| + 3000 sp              | 23.4 s (×7.9/2×)   |
| + 6 KB sp              | 185 s              |
| ~100 KB sp             | hours              |&lt;/p&gt;
&lt;p&gt;Fully R…&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;### Summary&lt;/p&gt;
&lt;p&gt;Two regular expressions used while parsing email headers backtrack
polynomially on attacker-controlled input. Parsing a single small, well-formed
email can consume minutes to hours of CPU, denying service to any process that
parses untrusted mail.&lt;/p&gt;
&lt;p&gt;Both are reachable from an ordinary `parse_from_string()`, `parse_from_bytes()`
or `parse_from_file()` call — no special API, option, or malformed structure is
required by the victim.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**1. Address-header fallback regex (`src/mailparser/utils.py`)**&lt;/p&gt;
&lt;p&gt;`get_addresses()` falls back to `_ADDR_FALLBACK_RE` whenever
`email.utils.getaddresses(strict=True)` yields no usable address. The
alternative `([^&amp;lt;,]*?)\s*&amp;lt;([^&amp;gt;]+)&amp;gt;` overlaps a lazy quantifier with an adjacent
`\s*` — a space matches both. Driven by `finditer`, which retries at every
offset and rescans the remainder, matching degrades to **quadratic** on `&amp;lt;`
padding and **cubic** on whitespace padding.&lt;/p&gt;
&lt;p&gt;The fallback engages on the feature&amp;#39;s own happy path, e.g.
`From: alice@example.com &amp;lt;bob@example.com&amp;gt;`.&lt;/p&gt;
&lt;p&gt;Measured (4.6.0, CPython 3.14, macOS arm64; reproduced identically on Linux and
on CPython 3.9, 3.11, 3.12, 3.13):&lt;/p&gt;
&lt;p&gt;| Padding                | Parse time         |
| ---------------------- | ------------------ |
| valid address + 750 sp | 0.38 s             |
| + 1500 sp              | 2.97 s             |
| + 3000 sp              | 23.4 s (×7.9/2×)   |
| + 6 KB sp              | 185 s              |
| ~100 KB sp             | hours              |&lt;/p&gt;
&lt;p&gt;Fully R…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r7w7-vpq8-c5vv</guid>
    </item>
  </channel>
</rss>
