# CVE-2026-23760: SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel

> Unauthenticated attackers can reset administrator passwords via the API, gaining full administrative control and executing system commands.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 26 Jan 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-mj6x-679w-76wr

## What is CVE-2026-23760?

CVE-2026-23760 is a critical authentication bypass vulnerability in SmarterTools SmarterMail, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-23760?

It affects 1 product.


Products: Smartertools Smartermail.

## How do I fix CVE-2026-23760?

No fix has been published for CVE-2026-23760 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 16 Feb 2026.

## Is CVE-2026-23760 being exploited?

Yes. Attackers have exploited CVE-2026-23760 in the wild since at least 26 Jan 2026, including in ransomware campaigns.

Public exploit code:

- CVE-2026-23760 - An authentication bypass via password reset API in SmarterMail. (github_poc): https://github.com/MaxMnMl/smartermail-CVE-2026-23760-poc
- CVE-2026-0001. Do with your own risk (github_poc): https://github.com/HORKimhab/CVE-2026-0001
- SmarterTools SmarterMail - Admin Password Reset (nuclei): http/cves/2026/CVE-2026-23760.yaml

## Other vulnerabilities in SmarterTools SmarterMail

- [CVE-2025-52691](https://insights.sbomify.com/CVE-2025-52691/): SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type (critical 10.0, exploited in the wild)
- [CVE-2026-24423](https://insights.sbomify.com/CVE-2026-24423/): SmarterTools SmarterMail Missing Authentication for Critical Function (critical 9.3, exploited in the wild)
- [CVE-2021-32234](https://insights.sbomify.com/CVE-2021-32234/): Code injection in n/a (critical 9.8)
- [CVE-2019-7214](https://insights.sbomify.com/CVE-2019-7214/): Deserialization in n/a (critical 9.8)
- [CVE-2026-7807](https://insights.sbomify.com/CVE-2026-7807/): SmarterTools SmarterMail < Build 9560 Server Local File Inclusion via the /api/v1/report/summary/{type} API (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23760 and fix it if it is affected.

What it is: CVE-2026-23760 is a critical authentication bypass vulnerability in SmarterTools SmarterMail, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-23760 in the wild since at least 26 Jan 2026, including in ransomware campaigns.

Affected product: SmarterTools SmarterMail. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23760/ (Markdown: https://insights.sbomify.com/CVE-2026-23760/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23760
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23760
- OSV: https://osv.dev/vulnerability/CVE-2026-23760

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23760/
Summaries are generated and may contain mistakes; the official description above is the record.