<?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 13:50:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-107587 — Improper Certificate Validation in hMailServer</title>
      <link>https://db.gcve.eu/vuln/cve-2026-107587</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Progressive Robot Ltd hMailServer&lt;/p&gt;
&lt;p&gt;Improper certificate validation in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote unauthenticated attacker to have S/MIME-encrypted mail that the account later sends to another correspondent also encrypted to the attacker&amp;#39;s key. When its recipient opened a signed message, the webmail kept the signer&amp;#39;s certificate for encrypting replies whether or not the server found its chain trusted, under the first e-mail address the certificate listed rather than the message&amp;#39;s From address, and beside any certificate already held for that address. Encrypted mail later sent from the webmail to that address was encrypted to every certificate held for it, so a holder of the kept certificate&amp;#39;s key who obtains a copy of such a message can read it.&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;Improper certificate validation in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote unauthenticated attacker to have S/MIME-encrypted mail that the account later sends to another correspondent also encrypted to the attacker&amp;#39;s key. When its recipient opened a signed message, the webmail kept the signer&amp;#39;s certificate for encrypting replies whether or not the server found its chain trusted, under the first e-mail address the certificate listed rather than the message&amp;#39;s From address, and beside any certificate already held for that address. Encrypted mail later sent from the webmail to that address was encrypted to every certificate held for it, so a holder of the kept certificate&amp;#39;s key who obtains a copy of such a message can read it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-107587</guid>
    </item>
  </channel>
</rss>
