CVE-2026-24423: Unauthenticated RCE in SmarterMail ConnectToHub API
- Vendor
- Smartertools
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.
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.
Exploits
3 exploits validated by Mallory's analysis.
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.
References
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.
Recent activity
93 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.