SmarterTools SmarterMail < Build 9511 Unauthenticated RCE via ConnectToHub API
SmarterMail builds prior to build 9511 are affected, and the fix is build 9511. No vendor severity rating is given, only the CVSS score of 9.3.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 100.0.9511
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SmarterTools SmarterMail, an email server platform, is affected by this flaw. An attacker who can reach the server without logging in could run arbitrary commands on the underlying system, potentially taking full control of the mail server.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
SmarterTools SmarterMail versions prior to build 9511 contain an unauthenticated remote code execution vulnerability in the ConnectToHub API method. The attacker could point the SmarterMail to the malicious HTTP server, which serves the malicious OS command. This command will be executed by the vulnerable application.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- SmarterTools SmarterMail
fixed in 100.0.9511
References 3
Questions about CVE-2026-24423
What does this mean?
The ConnectToHub API can be made to have SmarterMail connect to a malicious HTTP server, which serves an OS command. The vulnerable application then executes that command, and the attack needs no login.Source: vulncheck.com
Am I affected, and how do I check?
SmarterMail builds prior to build 9511 are in the affected range. To check, compare the installed SmarterMail build number with 9511.Source: vulncheck.com
What should I do about it?
Upgrade SmarterMail to build 9511 or later, which is the fixed version.Source: vulncheck.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-05, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data