SMTP service in SmarterTools SmarterMail 1.6.1511 and 1.6.1529 allows remote attackers to cause a denial of service (CPU consumption) via a
SMTP service in SmarterTools SmarterMail 1.6.1511 and 1.6.1529 allows remote attackers to cause a denial of service (CPU consumption) via a large number of simultaneous open connections to TCP port 25.
- Published
- Dec 31, 2004
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| smartertools | smartermail | cpe:2.3:a:smartertools:smartermail |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- smartertools smartermail1.6.1511
- smartertools smartermail1.6.1529
Same product
smartertools: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-23760SmarterTools SmarterMail < Build 9511 Authentication Bypass via Password Reset APIKEV96Now
- CVE-2025-52691Upload Arbitrary FilesKEV96Now
- CVE-2026-24423SmarterTools SmarterMail < Build 9511 Unauthenticated RCE via ConnectToHub APIKEV93Now
- CVE-2019-7214SmarterTools SmarterMail 16.x before build 6985 allows deserialization of untrusted data.64This week
- CVE-2021-32234SmarterTools SmarterMail 16.x through 100.x before 100.0.7803 allows remote code execution.40Plan
- CVE-2019-7213SmarterTools SmarterMail 16.x before build 6985 allows directory traversal.38Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- members.lycos.co.uk/r34ct/main/smarter_mail%203.1/smarter_mail.txt
- secunia.com/advisories/11042
- www.zone-h.org/advisories/read/id=4098
- exchange.xforce.ibmcloud.com/vulnerabilities/15391
Vendor advisories and official records. Exploit/PoC links are deliberately left out.