<?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>Thu, 05 Nov 2026 12:33:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-114490 — Incorrect Authorization in hMailServer</title>
      <link>https://db.gcve.eu/vuln/cve-2026-114490</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Progressive Robot Ltd hMailServer&lt;/p&gt;
&lt;p&gt;Incorrect authorization in the COM administration API of Progressive Robot hMailServer 6.3.4 through 6.3.6 allows an account assigned the serveradmin role with a list of domains - a credential an administrator may create meaning to confine it to those domains - to act as the whole-server administrator over COM. Administrator roles are meant to confine such a credential to the domains its list names, and the REST API did not take it for the server administrator, but the COM API&amp;#39;s server-administrator check read the administer_server permission as the whole server whatever list the grant carried. So the credential signed in through the Control Panel, or through a script run on the server, as the server administrator of every domain: it could read and change every domain&amp;#39;s accounts and mail, rename any domain, map a domain alias onto any, write the server&amp;#39;s settings and secrets, and create further server-administrator accounts. The COM API&amp;#39;s domain-administrator check, asked with no domain, likewise let an account assigned the domainadmin role with a list of domains that leaves out the account&amp;#39;s own domain administer that domain&amp;#39;s ordinary accounts over COM. An account holding serveradmin with no list is the server administrator by design and is unaffected, as are the help desk, auditor and custom roles.&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;Incorrect authorization in the COM administration API of Progressive Robot hMailServer 6.3.4 through 6.3.6 allows an account assigned the serveradmin role with a list of domains - a credential an administrator may create meaning to confine it to those domains - to act as the whole-server administrator over COM. Administrator roles are meant to confine such a credential to the domains its list names, and the REST API did not take it for the server administrator, but the COM API&amp;#39;s server-administrator check read the administer_server permission as the whole server whatever list the grant carried. So the credential signed in through the Control Panel, or through a script run on the server, as the server administrator of every domain: it could read and change every domain&amp;#39;s accounts and mail, rename any domain, map a domain alias onto any, write the server&amp;#39;s settings and secrets, and create further server-administrator accounts. The COM API&amp;#39;s domain-administrator check, asked with no domain, likewise let an account assigned the domainadmin role with a list of domains that leaves out the account&amp;#39;s own domain administer that domain&amp;#39;s ordinary accounts over COM. An account holding serveradmin with no list is the server administrator by design and is unaffected, as are the help desk, auditor and custom roles.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-114490</guid>
    </item>
  </channel>
</rss>
