Skip to main content
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Unauthenticated RCE in SmarterTools SmarterMail ConnectToHub API

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 described as a missing authentication check for a critical function. A remote attacker can invoke ConnectToHub without valid credentials and direct the SmarterMail instance to connect to an attacker-controlled HTTP server. That server can then supply a malicious operating system command, which the vulnerable application executes on the SmarterMail host.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, 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 execute arbitrary OS commands in the context of the vulnerable application, leading to full server compromise, malware or ransomware deployment, persistence, lateral movement, and disruption of mail services and adjacent infrastructure. Multiple sources in the provided content state the vulnerability has been actively exploited in the wild, including in ransomware campaigns, and CISA added it to the KEV catalog.

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 feasible, limit exposure of SmarterMail to untrusted networks, and enforce outbound egress controls so the server cannot make HTTP connections to attacker-controlled or unapproved hosts. Segment mail servers from internal networks to reduce lateral movement risk, monitor for suspicious ConnectToHub requests and unexpected outbound callbacks, and investigate for compromise if the instance was internet-exposed on a vulnerable build.

Remediation

Patch, then assume compromise.

Upgrade SmarterTools SmarterMail to build 9511 or later. The provided content also notes administrators were later advised to update to the latest available build, including build 9526, to address this and other recently fixed issues. Verify that all SmarterMail instances, including unmanaged or forgotten VMs, are updated and exposed ConnectToHub functionality is no longer reachable on vulnerable builds.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2026-24423MaturityPoCVerified exploit

Repository 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).

aavaminDisclosed Jan 29, 2026pythonmarkdownnetwork (SSRF/trust-boundary violation leading to potential RCE via attacker-controlled hub response)
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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence9

Every observed campaign linking this CVE to a named adversary.

Associated malware17

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity66

Community discussion across Reddit, Mastodon, and other social sources.

Unauthenticated RCE in SmarterTools SmarterMail ConnectToHub API (CVE-2026-24423) | Mallory