Quick answers
- Is CVE-2026-92595 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92595 being exploited in the wild.
- How severe is CVE-2026-92595?
- Medium severity, with a CVSS score of 5.9, published 16 September 2026.
- Which products and versions are affected?
- Nodemailer <= 9.1.0.
- Is there a fix for CVE-2026-92595?
- A patch was published on 2026-09-01: Patched in version 9.1.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92595 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92595?
- Check whether you run Nodemailer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a security sandbox bypass in the MailMessage.resolveContent() public API. When called with the documented legacy 3-argument signature (data, key, callback), the function fails to pass the transporter-level disableFileAccess and disableUrlAccess flags to the underlying shared.resolveContent() function, which normalizes missing options to an empty object. As a result, resolveContentValue skips access-control guards and reaches nmfetch() for SSRF or fs.createReadStream() for arbitrary file reads. The vulnerability affects applications that use the public plugin API to resolve message content; direct transporter.sendMail() calls are unaffected because they use internal code paths that correctly thread the flags. The issue was introduced by a previous GHSA-wqvq-jvpq-h66f fix and persists in version 9.1.0. Patch version 9.1.1 is available.
Affected products
- Nodemailer Nodemailer <= 9.1.0
Identifiers
- CVE-2026-92595
- GHSA-8m3c-c648-2xjj
Timeline
- 2026-09-08: disclosed
- 2026-09-01: patched: Patched in version 9.1.1