CVE-2026-92595
MEDIUMDescription
Nodemailer (npm package `nodemailer`) versions 9.1.0 and earlier do not honor the `disableFileAccess` and `disableUrlAccess` sandbox options when message content is resolved through the public plugin API `MailMessage.resolveContent()` using the documented legacy three-argument signature `resolveContent(data, key, callback)`. Because `shared.resolveContent()` normalizes the missing `options` argument to an empty object, the message-level flags copied into `mail.data` by the MailMessage constructor are discarded, and `resolveContentValue()` skips both access-control checks, reaching `nmfetch(url)` or `fs.createReadStream(path)`. As a result, plugin or application code that resolves untrusted message content (html, text, attachment `path` or `href`) via this API can be induced to read arbitrary local files or issue outbound HTTP(S) requests (server-side request forgery), bypassing the sandbox the application enabled. The internal paths used by `transporter.sendMail()` (`resolveAll()`, `_convertDataImages()`, and the MIME streaming path) are not affected. Fixed in version 9.1.1.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 10% of all known CVEs.
References
Related Vulnerabilities
Other CWE-73 (External Control of File Name or Path) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-39952 | Critical | 9.8 | 100% | - | Fix |
| CVE-2024-8517 | Critical | 9.8 | 95% | - | Fix |
| CVE-2025-33053 | High | 8.8 | 88% | KEV | Fix |
| CVE-2023-4634 | Critical | 9.8 | 86% | - | Fix |
| CVE-2024-43451 | Medium | 6.5 | 84% | KEV | Fix |
| CVE-2018-17246 | Critical | 9.8 | 82% | - | Fix |
Common questions
How do I fix CVE-2026-92595?
Upgrade node-nodemailer on debian unstable to 10.0.0+~8.0.1-1 or later.
Is CVE-2026-92595 being actively exploited?
Not that we know of. CVE-2026-92595 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.19% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.
How severe is CVE-2026-92595?
CVE-2026-92595 has a CVSS v3 base score of 5.9, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-92595 affect?
Published advisories record a fix for node-nodemailer (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-92595
Markdown
[](https://tridentstack.com/cve/CVE-2026-92595)HTML
<a href="https://tridentstack.com/cve/CVE-2026-92595"><img src="https://tridentstack.com/cve/badge/CVE-2026-92595.svg" alt="CVE-2026-92595"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-16.