<?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>Sat, 14 Nov 2026 03:24:41 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-104082</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-104082</link>
      <description>&lt;p&gt;SmarterMail before build 9777 contains a remote code execution vulnerability that allows an attacker holding a SysAdmin-scoped access token to bypass the Volume Mount script-directory containment control by provisioning a new mail domain with an arbitrary FileStore root path inside the trusted Scripts directory via the domain-put endpoint. Attackers can disclose the Scripts path through the AddOrUpdateMount endpoint, clear the upload extension blacklist via the global-mail endpoint, then upload a malicious script through the ordinary mail file-storage upload API so that saving a CommandMount triggers RunScript before validation, resulting in a reverse shell executing as the SmarterMail service account with SYSTEM-level privileges.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SmarterMail before build 9777 contains a remote code execution vulnerability that allows an attacker holding a SysAdmin-scoped access token to bypass the Volume Mount script-directory containment control by provisioning a new mail domain with an arbitrary FileStore root path inside the trusted Scripts directory via the domain-put endpoint. Attackers can disclose the Scripts path through the AddOrUpdateMount endpoint, clear the upload extension blacklist via the global-mail endpoint, then upload a malicious script through the ordinary mail file-storage upload API so that saving a CommandMount triggers RunScript before validation, resulting in a reverse shell executing as the SmarterMail service account with SYSTEM-level privileges.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-104082</guid>
    </item>
    <item>
      <title>GCVE-1988-2026-0493 — SmarterMail &lt;9777 Pre-Auth RCE (half click lol): CVE-2026-104082, CVE-2026-104083, CVE-2026-104084</title>
      <link>https://db.gcve.eu/vuln/gcve-1988-2026-0493</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; unknown SmarterMail &amp;lt;9777 Pre-Auth&lt;/p&gt;
&lt;p&gt;original blog: https://blog.evan.lat/posts/sm/&lt;/p&gt;
&lt;p&gt;SUMMARY: multiple vulns and misconfigurations in smartermail, notably
a mxss and session persistence issues, alongside several logic bugs
can be chained to achieve remote code execution as nt
authority\system;
https://nvd.nist.gov/vuln/detail/CVE-2026-104082
https://nvd.nist.gov/vuln/detail/CVE-2026-104083
https://nvd.nist.gov/vuln/detail/CVE-2026-104084&lt;/p&gt;
&lt;p&gt;a mutated xss exists in smartermail. by sending a specific
text/calendar (icalendar) mimetype with the x-alt-desc header set to a
mutated xss payload:
&amp;lt;math&amp;gt;&amp;lt;mtext&amp;gt;&amp;lt;mglyph&amp;gt;&amp;lt;style&amp;gt;&amp;lt;img src=x onerror=&amp;#34;{js}&amp;#34;&amp;gt;&amp;lt;/style&amp;gt;&lt;/p&gt;
&lt;p&gt;the parser in the handrolled sanitizer of smartermail fails to
properly sanitize this. the payload reforms after attempts at parsing
it, allowing us to circumvent pre-auth with just one viewing of an
email. notably, this can be done entirely without clicking as well
(technically), since smartermail seems to open to latest email
automatically&lt;/p&gt;
&lt;p&gt;====================&lt;/p&gt;
&lt;p&gt;a session logic vuln exists in smartermail. getting the refresh token
of a domain admin before they are subsequently demoted does not
actually invalidate any of the tokens privileges; meaning you can
replay the token and continue retaining domain admin/sysadmin even
after being demoted by simply posting the refresh token to
/api/v1/auth/refresh-token and getting new accesstoken/refreshtoken
pairs with the same roles&lt;/p&gt;
&lt;p&gt;====================&lt;/p&gt;
&lt;p&gt;a series of logic vulns exist in smartermail that can lead to rce a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; unknown SmarterMail &amp;lt;9777 Pre-Auth&lt;/p&gt;
&lt;p&gt;original blog: https://blog.evan.lat/posts/sm/&lt;/p&gt;
&lt;p&gt;SUMMARY: multiple vulns and misconfigurations in smartermail, notably
a mxss and session persistence issues, alongside several logic bugs
can be chained to achieve remote code execution as nt
authority\system;
https://nvd.nist.gov/vuln/detail/CVE-2026-104082
https://nvd.nist.gov/vuln/detail/CVE-2026-104083
https://nvd.nist.gov/vuln/detail/CVE-2026-104084&lt;/p&gt;
&lt;p&gt;a mutated xss exists in smartermail. by sending a specific
text/calendar (icalendar) mimetype with the x-alt-desc header set to a
mutated xss payload:
&amp;lt;math&amp;gt;&amp;lt;mtext&amp;gt;&amp;lt;mglyph&amp;gt;&amp;lt;style&amp;gt;&amp;lt;img src=x onerror=&amp;#34;{js}&amp;#34;&amp;gt;&amp;lt;/style&amp;gt;&lt;/p&gt;
&lt;p&gt;the parser in the handrolled sanitizer of smartermail fails to
properly sanitize this. the payload reforms after attempts at parsing
it, allowing us to circumvent pre-auth with just one viewing of an
email. notably, this can be done entirely without clicking as well
(technically), since smartermail seems to open to latest email
automatically&lt;/p&gt;
&lt;p&gt;====================&lt;/p&gt;
&lt;p&gt;a session logic vuln exists in smartermail. getting the refresh token
of a domain admin before they are subsequently demoted does not
actually invalidate any of the tokens privileges; meaning you can
replay the token and continue retaining domain admin/sysadmin even
after being demoted by simply posting the refresh token to
/api/v1/auth/refresh-token and getting new accesstoken/refreshtoken
pairs with the same roles&lt;/p&gt;
&lt;p&gt;====================&lt;/p&gt;
&lt;p&gt;a series of logic vulns exist in smartermail that can lead to rce a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/gcve-1988-2026-0493</guid>
    </item>
    <item>
      <title>GHSA-4rp5-r82m-g6p3</title>
      <link>https://db.gcve.eu/vuln/ghsa-4rp5-r82m-g6p3</link>
      <description>&lt;p&gt;SmarterMail before build 9777 contains a remote code execution vulnerability that allows an attacker holding a SysAdmin-scoped access token to bypass the Volume Mount script-directory containment control by provisioning a new mail domain with an arbitrary FileStore root path inside the trusted Scripts directory via the domain-put endpoint. Attackers can disclose the Scripts path through the AddOrUpdateMount endpoint, clear the upload extension blacklist via the global-mail endpoint, then upload a malicious script through the ordinary mail file-storage upload API so that saving a CommandMount triggers RunScript before validation, resulting in a reverse shell executing as the SmarterMail service account with SYSTEM-level privileges.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SmarterMail before build 9777 contains a remote code execution vulnerability that allows an attacker holding a SysAdmin-scoped access token to bypass the Volume Mount script-directory containment control by provisioning a new mail domain with an arbitrary FileStore root path inside the trusted Scripts directory via the domain-put endpoint. Attackers can disclose the Scripts path through the AddOrUpdateMount endpoint, clear the upload extension blacklist via the global-mail endpoint, then upload a malicious script through the ordinary mail file-storage upload API so that saving a CommandMount triggers RunScript before validation, resulting in a reverse shell executing as the SmarterMail service account with SYSTEM-level privileges.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-4rp5-r82m-g6p3</guid>
    </item>
  </channel>
</rss>
