# CVE-2026-92595 — nodemailer

> As of 2026-09-16, CVE-2026-92595 is a MEDIUM-severity vulnerability in nodemailer, CVSS v3.1 5.9. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-92595 as of 2026-09-16; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-16

## What is CVE-2026-92595?

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.

The record classifies CVE-2026-92595 under weakness class [CWE-73](https://intel.threadlinqs.com/cwe/CWE-73). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 19 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.9 — MEDIUM (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **CVSS v4.0 base score:** 6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-16

## Is CVE-2026-92595 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **nodemailer**: nodemailer

## How to fix CVE-2026-92595

No vendor patch reference has been recorded for CVE-2026-92595 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-92595

No threat campaign in the Threadlinqs corpus currently references CVE-2026-92595, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-09-17. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/nodemailer/nodemailer/security/advisories/GHSA-8m3c-c648-2xjj)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/nodemailer-before-9.1.1-security-sandbox-bypass-via-resolvecontent)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-92595
Full detection coverage and IOCs for threats exploiting CVE-2026-92595 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp