CriticalCVE-2026-23760

    SmarterTools SmarterMail < Build 9511 Authentication Bypass via Password Reset API (CVE-2026-23760)

    Published In CISA KEV since Sources: CVE.org, pwn.watch

    What is affected, what to do

    The vulnerability CVE-2026-23760 is an authentication bypass in SmarterTools SmarterMail's password reset API. An unauthenticated attacker can reset administrator accounts by providing a username and new password, leading to full control of the SmarterMail instance. This vulnerability is actively exploited in ransomware campaigns and is listed in the CISA KEV catalog. Affected are versions prior to build 9511. Immediate patching to version 100.0.9511 is critical to prevent administrative compromise.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update SmarterTools SmarterMail to version 100.0.9511. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • SmarterTools SmarterMail lt *..100.0.9511
    Fixed in
    • SmarterTools SmarterMail 100.0.9511

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, pwn.watch

    96.4 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.88

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    267.62 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    96.4 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.88
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-288

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw is reachable over the network with no authentication and no user interaction. It is trivially automatable: a single request carrying an admin username and a new password is enough. Through SmarterMail's built-in management features, it leads straight to highest-privilege code execution on the host. It sits among the CVEs most likely to be exploited, and CISA confirms use in ransomware campaigns. Typical targets are self-hosted mail servers at SMEs, hosting providers and public-sector bodies. Treat any internet-facing SmarterMail instance below build 9511 as a top-priority emergency and assume it is compromised until proven otherwise.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch now: Every SmarterMail instance below build 9511 is vulnerable. Upgrade to build 9511 or later immediately. Check the SmarterTools vendor advisory for the latest build and prefer it. Verify the installer against the official vendor download before deploying.
      • Cut exposure: If you cannot upgrade within hours, block internet access to the SmarterMail web interface and API (HTTP/HTTPS) at the perimeter firewall. Alternatively, restrict access to admin source networks or VPN. SMTP, IMAP and POP3 can stay open to keep mail flowing.
      • Check for compromise before patching: Look in web server and SmarterMail logs for requests to force-reset-password from unknown source IPs. If you find any, treat the box as compromised. Isolate the host and preserve evidence (memory image, logs, SmarterMail configuration directory) rather than simply patching over it.
      • Rotate credentials: Reset passwords on all SmarterMail system administrator accounts. Also rotate every credential stored on or used by the host: service accounts, SMTP relay credentials, and domain accounts that log on to it.
      • Audit admin accounts: Reconcile the system admin list against your known-good baseline. Disable and document any unknown accounts.
      • Prepare for reporting: Exploitation yields SYSTEM/root code execution, and CISA flags use in ransomware campaigns. On confirmed compromise, prepare the NIS2 early warning to your CSIRT/BSI within 24 hours.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the SmarterMail host in a DMZ zone with no direct path to domain controllers, file servers or backup infrastructure. Restrict host egress to SMTP (25/587) and required update destinations, and deny everything else. This hampers reverse shells and payload staging.
      • WAF/reverse proxy: Front the server with a reverse proxy (IIS ARR, nginx or a WAF). Deny any request whose URI path contains force-reset-password unless it originates from the admin network. Add rate limiting on all API paths containing auth or password.
      • IPS signature: Add a local Suricata/Snort rule: alert http any any -> $SMARTERMAIL_SERVERS any (msg:"SmarterMail force-reset-password anon"; http.uri; content:"force-reset-password"; nocase; sid:9000001;). Run it in alert mode first, then switch to drop once validated.
      • Endpoint hardening: Where the vendor supports it, run the SmarterMail service under a dedicated low-privilege account instead of LocalSystem. Use EDR custom rules or AppLocker/WDAC to block child processes of the SmarterMail service (cmd.exe, powershell.exe, rundll32.exe, certutil.exe).
      • IAM: Minimise the number of system admin accounts and avoid predictable usernames such as admin. Enable multi-factor authentication for admin accounts where available.
      • Backup protection: Verify offline or immutable backups of the mail store and configuration, given the confirmed ransomware use.
    3. Runbook step 3

      Detection rules

      • Web server logs (IIS W3C / SmarterMail logs): POST requests to URIs containing force-reset-password from external IPs, especially without a prior successful login from the same source. SPL: index=web uri_path="*force-reset-password*" | stats count by src_ip, uri_path, status
      • Admin login anomaly: A successful system admin login shortly after a password reset, from a new source IP or ASN. Correlate these events in the SmarterMail administrative logs.
      • EDR/Sysmon process ancestry (Sysmon EID 1, Security EID 4688): The SmarterMail service process (typically MailService.exe) spawning cmd.exe, powershell.exe, whoami.exe or net.exe. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "MailService.exe" and FileName in~ ("cmd.exe","powershell.exe","whoami.exe","net.exe")
      • Persistence: New services (System EID 7045), scheduled tasks (Security EID 4698) or new local accounts (EID 4720) on the mail host shortly after a reset event.
      • Network telemetry (Zeek/Suricata): Outbound connections from the mail host to unfamiliar destinations on non-mail ports. Unusual outbound data volumes suggest pre-encryption exfiltration.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    SmarterTools SmarterMail versions prior to build 9511 contain an authentication bypass vulnerability in the password reset API. The force-reset-password endpoint permits anonymous requests and fails to verify the existing password or a reset token when resetting system administrator accounts. An unauthenticated attacker can supply a target administrator username and a new password to reset the account, resulting in full administrative compromise of the SmarterMail instance. NOTE: SmarterMail system administrator privileges grant the ability to execute operating system commands via built-in management functionality, effectively providing administrative (SYSTEM or root) access on the underlying host.

    Source: CISA KEV Catalog, NVD (NIST), CVE.org (MITRE), pwn.watch, cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    SmarterToolsSmarterMail
    • < 100.0.9511
    • 100.0.9511
    smartertoolssmartermail
    • < 100.0.9511
    • 100.0.9511

    Vendors and products

    Weakness classes (CWE)

    • CWE-288Authentication Bypass Using an Alternate Path or Channel

      Base

      The product requires authentication, but the product has an alternate path or channel that does not require authentication.

      Entry at MITRE CWE-288

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    Reference tagged as exploitlabs.watchtowr.com (opens in a new tab)PoC (publicly reported)reported, not verified—

    References & sources

    • smartertools.comSmarterTools SmarterMail — CVE-2025-52691Release notes, Patch, pwn-watch
    • labs.watchtowr.comattackers-with-decompilers-strike-again-smartertools-smartermai…Technical description, Exploit
    • code-white.compublic-vulnerability-listThird-party advisory
    • vulncheck.comadvisories/smartertools-smartermail-authentication-bypass-via-p…Third-party advisory
    • huntress.comblog/smartermail-account-takeover-leading-to-rceThird-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-23760government-resource
    • pwn.watchpwn.watch: SmarterTools SmarterMail: SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type Vulnerabilitypwn-watch
    • NVD (NIST)NVD: CVE-2025-52691pwn-watch
    • NVD (NIST)NVD: CVE-2026-23760pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-23760
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-23760"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-23760.svg?lang=en" alt="CVE-2026-23760 – NEOSEC Intel" height="20"></a>