<?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, 21 Nov 2026 10:40:33 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407011</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407011</link>
      <description>EUVD-2026-407011</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407011</guid>
    </item>
    <item>
      <title>fkie_cve-2026-129307</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-129307</link>
      <description>&lt;p&gt;eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. In 3.0.3 and earlier, eml_parser.routing.parserouting() in eml_parser/routing.py builds a regular expression with multiple greedy capture groups and appends the npdate date literal extracted from a normalized copy of an attacker-controlled Received header, then searches that expression against the original unnormalized line. A formatting difference can make the trailing literal impossible to match, causing exhaustive backtracking across the greedy groups at each start position. The unsliced Received-header path is invoked by decode_email, decode_email_bytes, and parse_email, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. In 3.0.3 and earlier, eml_parser.routing.parserouting() in eml_parser/routing.py builds a regular expression with multiple greedy capture groups and appends the npdate date literal extracted from a normalized copy of an attacker-controlled Received header, then searches that expression against the original unnormalized line. A formatting difference can make the trailing literal impossible to match, causing exhaustive backtracking across the greedy groups at each start position. The unsliced Received-header path is invoked by decode_email, decode_email_bytes, and parse_email, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-129307</guid>
    </item>
    <item>
      <title>GHSA-m4g8-47f9-h588 — eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m4g8-47f9-h588</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: eml-parser&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`eml_parser.routing.parserouting()` dynamically builds a regex from up to four greedy `.*` groups (`from (?P&amp;lt;from&amp;gt;.*)by (?P&amp;lt;by&amp;gt;.*)with (?P&amp;lt;with&amp;gt;.*)for (?P&amp;lt;for&amp;gt;.*)`) terminated by an escaped literal of the date extracted from a **normalized** copy of the `Received` header. Because the date literal comes from the normalized text but is searched in the original line, a crafted header can make the trailing literal unmatchable; the search then fails at every start position only after exhaustively backtracking the four nested greedy groups — **O(n^4)** in header length. A single ~5.9 KB email pins one CPU core for ~12 seconds; doubling the input multiplies the cost ~25x, so a ~13 KB header takes minutes and a ~25 KB header effectively hangs the parse worker.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Root cause: `eml_parser/routing.py:140-148` (v3.0.3):&lt;/p&gt;
&lt;p&gt;```python
reg = &amp;#39;&amp;#39;
for item in tout:
    reg += item[1] + &amp;#39;(?P&amp;lt;&amp;#39; + item[1].strip() + &amp;#39;&amp;gt;.*)&amp;#39;   # e.g. &amp;#39;from (?P&amp;lt;from&amp;gt;.*)&amp;#39;
if npdate:
    reg += eml_parser.regexes.escape_special_regex_chars.sub(r&amp;#34;&amp;#34;&amp;#34;\\\1&amp;#34;&amp;#34;&amp;#34;, npdate)
reparse = re.compile(reg)
reparseg = reparse.search(line)   # searched in the ORIGINAL line
```&lt;/p&gt;
&lt;p&gt;`npdate` is extracted from `npline`, a normalized copy of the header (spacing added around `(`, `)`, `;` at routing.py:79-81; parenthesized text removed at line 82; whitespace collapsed at line 83), so it is not guaranteed to be a substring of `line`. An unbalanced `(` in the date tail (e.g. `+0000(comment`) becomes ` ( comment` in `npline`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: eml-parser&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`eml_parser.routing.parserouting()` dynamically builds a regex from up to four greedy `.*` groups (`from (?P&amp;lt;from&amp;gt;.*)by (?P&amp;lt;by&amp;gt;.*)with (?P&amp;lt;with&amp;gt;.*)for (?P&amp;lt;for&amp;gt;.*)`) terminated by an escaped literal of the date extracted from a **normalized** copy of the `Received` header. Because the date literal comes from the normalized text but is searched in the original line, a crafted header can make the trailing literal unmatchable; the search then fails at every start position only after exhaustively backtracking the four nested greedy groups — **O(n^4)** in header length. A single ~5.9 KB email pins one CPU core for ~12 seconds; doubling the input multiplies the cost ~25x, so a ~13 KB header takes minutes and a ~25 KB header effectively hangs the parse worker.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Root cause: `eml_parser/routing.py:140-148` (v3.0.3):&lt;/p&gt;
&lt;p&gt;```python
reg = &amp;#39;&amp;#39;
for item in tout:
    reg += item[1] + &amp;#39;(?P&amp;lt;&amp;#39; + item[1].strip() + &amp;#39;&amp;gt;.*)&amp;#39;   # e.g. &amp;#39;from (?P&amp;lt;from&amp;gt;.*)&amp;#39;
if npdate:
    reg += eml_parser.regexes.escape_special_regex_chars.sub(r&amp;#34;&amp;#34;&amp;#34;\\\1&amp;#34;&amp;#34;&amp;#34;, npdate)
reparse = re.compile(reg)
reparseg = reparse.search(line)   # searched in the ORIGINAL line
```&lt;/p&gt;
&lt;p&gt;`npdate` is extracted from `npline`, a normalized copy of the header (spacing added around `(`, `)`, `;` at routing.py:79-81; parenthesized text removed at line 82; whitespace collapsed at line 83), so it is not guaranteed to be a substring of `line`. An unbalanced `(` in the date tail (e.g. `+0000(comment`) becomes ` ( comment` in `npline`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m4g8-47f9-h588</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-129307 — eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-129307</link>
      <description>msrc_CVE-2026-129307</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-129307</guid>
    </item>
  </channel>
</rss>
