Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-24423: Unauthenticated RCE in SmarterMail ConnectToHub API

Published Jan 23, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS88.2%100th percentile
CISA KEVYesAdded Feb 5, 2026
In the wildActivePer CISA KEV
Vendor
Smartertools
IdentifiersCVE-2026-24423CWE-306 · Missing Authentication for…

CVE-2026-24423 is a critical unauthenticated remote code execution vulnerability in SmarterTools SmarterMail affecting versions prior to build 9511. The flaw is in the ConnectToHub API method and is caused by a missing authentication check on a critical function. A remote attacker can invoke this API without valid credentials and direct the SmarterMail instance to connect to an attacker-controlled HTTP service. By supplying a malicious OS command through that remote service, the attacker can cause the vulnerable application to execute arbitrary operating system commands on the underlying server.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote code execution on the SmarterMail server. An attacker can run arbitrary OS commands in the security context of the vulnerable application, which can lead to full compromise of the mail server, deployment of additional payloads, theft or manipulation of mail-related data, establishment of persistence, and use of the compromised host as a foothold for lateral movement or ransomware operations.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict or disable access to the ConnectToHub API where operationally feasible, limit exposure of SmarterMail to untrusted networks, and enforce outbound network controls so the server cannot make arbitrary HTTP connections to attacker-controlled infrastructure. Segment mail servers from internal administrative infrastructure to reduce post-exploitation lateral movement, and monitor for suspicious use of the ConnectToHub functionality and unexpected child process or command execution from the SmarterMail service.

Remediation

Patch, then assume compromise.

Upgrade SmarterTools SmarterMail to build 9511 or later. Multiple references indicate build 9511 was the vendor fix for this vulnerability, and later builds also address additional SmarterMail security issues. Organizations should verify that all SmarterMail instances, including unmanaged or forgotten virtual machines, have been updated and should perform compromise assessment on systems that were exposed prior to patching because this vulnerability has been reported as actively exploited.

Public exploits

Exploits

3 exploits validated by Mallory's analysis.

View more in app →
SmarterMail-CVE-2026-24423The repository contains one executable Python file (MalHub.py) and a supporting README. It is a standalone, operational proof-of-concept for CVE-2026-24423, described as an unauthenticated SmarterTools SmarterMail ConnectToHub remote-code-execution issue affecting builds before 100.0.9511. MalHub.py starts an HTTP server on port 8081 and exclusively handles POST requests to /web/api/node-management/setup-initial-connection. Its response supplies a forged cluster/setup JSON structure containing SystemMount.CommandMount set to a Base64-encoded, hidden PowerShell command. The decoded PowerShell establishes a command-capable reverse TCP shell to the hardcoded attacker address 10.10.14.50 on port 4455. The script does not itself invoke the target's ConnectToHub endpoint and does not implement a TCP listener; an operator must separately cause the target to use the attacker hub and receive the callback. No exploit framework is used. The README documents the purported vulnerable target endpoint, affected version range, exploitation flow, and mitigation guidance.CyberAlp0 · Disclosed Sep 2, 2026 · python · powershell · network · webOperationalSmarterMail-CVE-2026-24423-The repository contains one executable Python proof-of-concept, MalHub.py, and a detailed README. It targets the claimed SmarterTools SmarterMail ConnectToHub unauthenticated RCE (CVE-2026-24423) on versions before build 9511. MalHub.py is not a complete initial-access client: it does not call the target's /api/v1/settings/sysadmin/connect-to-hub endpoint. Instead, it implements the attacker-side fake hub required after an operator causes a vulnerable SmarterMail server to connect to it. The server listens on TCP/8081 and only accepts POST requests for /web/api/node-management/setup-initial-connection. It responds with JSON containing SystemMount.Enabled=true, a writable Windows Temp mount path, and CommandMount set to a base64-encoded hidden PowerShell reverse-shell command. The embedded PowerShell payload connects back to the hardcoded 10.10.14.50:4455, executes received commands via iex, and sends command output to the attacker. This is an operational but environment-specific PoC: callback address, ports, and payload are hardcoded, and a separate TCP listener plus an external mechanism to invoke ConnectToHub are necessary.CyberAlp0 · Disclosed Sep 2, 2026 · python · markdown · networkOperationalCVE-2026-24423Repository purpose: a minimal proof-of-concept to reproduce CVE-2026-24423 in SmarterMail’s ConnectToHub workflow by standing up an attacker-controlled “Hub” HTTP service and then triggering the victim’s unauthenticated connect-to-hub API so the victim SSRFs to the hub and consumes a malicious JSON response. Structure: - CVE-2026-24423.py: Python3 HTTP server (http.server) that listens on 0.0.0.0:80 and only responds to POST /web/api/node-management/setup-initial-connection. It logs the received request body and returns a crafted JSON object containing fields like ClusterID/SharedSecret and, critically, SystemMount with MountPath "C:\\" and CommandMount "whoami > C:\\whoami.txt". This models the trust-boundary violation where the victim treats hub-provided configuration as authoritative and performs system-level actions. - README.md: Explains the vulnerability chain (unauthenticated admin interface + SSRF to attacker hub + hub response used for local operations → potential RCE). Provides a sample request to POST /api/v1/settings/sysadmin/connect-to-hub with hubAddress pointing to the attacker server. Exploit capabilities: - Acts as the attacker-controlled hub endpoint to deliver a malicious configuration payload. - Demonstrates a command-execution outcome (example Windows command writing whoami output to C:\\whoami.txt) if the target is vulnerable. Notes: - This repo does not include an automated client to send the trigger request; it relies on manual tooling (Burp/Yakit) per README. - The payload is hardcoded and Windows-oriented (C:\\ paths, cmd redirection).aavamin · Disclosed Jan 29, 2026 · python · markdown · network (SSRF/trust-boundary violation leading to potential RCE via attacker-controlled hub response)PoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SmartertoolsSmartermailapplication
FAQ

Frequently asked questions

Is CVE-2026-24423 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 5, 2026.
Is there a public exploit for CVE-2026-24423?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-24423, the earliest disclosed Jan 29, 2026.
Is there a patch for CVE-2026-24423?
Upgrade SmarterTools SmarterMail to build 9511 or later. Multiple references indicate build 9511 was the vendor fix for this vulnerability, and later builds also address additional SmarterMail security issues.
What products are affected by CVE-2026-24423?
Smartertools Smartermail.
How severe is CVE-2026-24423?
CVE-2026-24423 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 88.2% (100th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

93 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+20 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence9Every report linking this CVE to a named adversary.
Associated malware17Malware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity67Community discussion across Reddit, Mastodon, and other social sources.