# CVE-2026-25067: SmarterTools SmarterMail < Build 9518 Unauthenticated background-of-the-day Path Coercion

> Unauthenticated attackers can coerce SmarterMail to initiate SMB connections to attacker-controlled hosts, enabling NTLM relay and credential theft.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-x74x-r4q4-c3rw

## What is CVE-2026-25067?

CVE-2026-25067 is a medium-severity server-side request forgery vulnerability in SmarterTools SmarterMail, published on 29 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 9518  contain an unauthenticated path coercion vulnerability in the background-of-the-day preview endpoint. The application base64-decodes attacker-supplied input and uses it as a filesystem path without validation. On Windows systems, this allows UNC paths to be resolved, causing the SmarterMail service to initiate outbound SMB authentication attempts to attacker-controlled hosts. This can be abused for credential coercion, NTLM relay attacks, and unauthorized network authentication.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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

It affects 1 product.


Products: Smartertools Smartermail.

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

No fix has been published for CVE-2026-25067 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25067 being exploited?

There is no known exploitation of CVE-2026-25067 in the wild and no public exploit code.

## 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-2026-23760](https://insights.sbomify.com/CVE-2026-23760/): SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25067 is a medium-severity server-side request forgery vulnerability in SmarterTools SmarterMail, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25067 in the wild and no public exploit code.

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-25067/ (Markdown: https://insights.sbomify.com/CVE-2026-25067/index.md)
```

## Sources

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

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