<?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://db.gcve.eu</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>Sun, 11 Oct 2026 14:10:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-107572 — Inefficient Regular Expression Complexity in hMailServer</title>
      <link>https://db.gcve.eu/vuln/cve-2026-107572</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Progressive Robot Ltd hMailServer&lt;/p&gt;
&lt;p&gt;Inefficient complexity in the Sieve filter evaluation of Progressive Robot hMailServer 6.2.24 through 6.3.5 allows an authenticated account holder to make the mail services unavailable with their own filter. A &amp;#39;:matches&amp;#39; pattern was matched by a backtracking descent whose time grew with the matched value&amp;#39;s length raised to the number of wildcards, so a pattern such as &amp;#39;*a*a*a*b&amp;#39; over 800 characters took 44 seconds; and &amp;#39;deleteheader&amp;#39; erased the fields it removed one at a time, so removing many fields of one name over a message&amp;#39;s header cost O(N^2) (80,000 fields took 18.8 seconds). Sieve filters run on the small, shared delivery thread pool, so an account holder whose active script does this, fed a few messages they can send themselves, empties the pool and stops delivery for the whole server. The script is the account holder&amp;#39;s own and cannot be set for another user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Progressive Robot Ltd hMailServer&lt;/p&gt;
&lt;p&gt;Inefficient complexity in the Sieve filter evaluation of Progressive Robot hMailServer 6.2.24 through 6.3.5 allows an authenticated account holder to make the mail services unavailable with their own filter. A &amp;#39;:matches&amp;#39; pattern was matched by a backtracking descent whose time grew with the matched value&amp;#39;s length raised to the number of wildcards, so a pattern such as &amp;#39;*a*a*a*b&amp;#39; over 800 characters took 44 seconds; and &amp;#39;deleteheader&amp;#39; erased the fields it removed one at a time, so removing many fields of one name over a message&amp;#39;s header cost O(N^2) (80,000 fields took 18.8 seconds). Sieve filters run on the small, shared delivery thread pool, so an account holder whose active script does this, fed a few messages they can send themselves, empties the pool and stops delivery for the whole server. The script is the account holder&amp;#39;s own and cannot be set for another user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-107572</guid>
    </item>
  </channel>
</rss>
